For most of Halo's life, it's been a single agent doing everything. One loop, one model, one context window juggling reconnaissance, exploitation, and self-correction all at once. That's worked well enough to get 24 tools integrated and a functioning failure cache scoped per engagement, but it's starting to show the seams you'd expect from any single-agent system asked to do too many jobs at once: the context gets crowded, the reasoning gets muddier the longer an engagement runs, and a mistake in one phase (say, a bad recon assumption) quietly poisons every phase after it.
The next major milestone for Halo is multi-agent orchestration, and I want to talk through the shape of it without turning this into a design doc.
Why Split It Up At All
A pentest isn't really one task. It's five or six distinct kinds of thinking stitched together: figuring out what to do, deciding who does it and in what order, actually doing it, finding weaknesses worth pursuing, and — critically — recognizing when something didn't work and correcting course. Right now Halo does all of that inside a single loop with one shared context. It works, but it means the "attacking" mindset and the "planning" mindset are fighting for the same mental real estate. Anyone who's tried to both execute a task and audit their own execution at the same time knows how that goes.
