Manager Agents That Hire and Fire Their Own Workers: The First Framework Built for Continuous (Not One-Shot) Software Development

Manager Agents That Hire and Fire Their Own Workers: The First Framework Built for Continuous (Not One-Shot) Software Development

Nearly every agentic coding framework in production today was built to solve one-shot tasks: hand the agent a well-scoped ticket, receive a patch. That architecture breaks down the moment software development is what it actually is — iterative, multi-day, and evolving. Requirements shift mid-project. New complexity surfaces that wasn't visible at the start. A specialized authentication problem emerges three days in that nobody anticipated on day one. TheBotCompany is the first open-source framework designed explicitly for this reality, and its three architectural innovations each address a failure mode that one-shot systems simply cannot handle.

The first innovation is a three-phase state machine — Strategy, Execution, Verification — where milestone transitions are driven by validation rather than task completion. The agent doesn't just finish a subtask; it verifies against project goals and plans the next milestone before proceeding. The second is self-organizing agent teams: manager agents dynamically hire, assign roles to, and fire worker agents based on what the current project actually needs. When a security-sensitive task emerges mid-project, the manager spins up a specialist; once the task is done, the worker is released. Team composition is fluid rather than fixed at project start. The third is an async human oversight model: engineers check in at milestone boundaries, redirect and approve, then disengage. They're milestone reviewers, not session monitors — which is likely how most teams will eventually want to operate coding agents on larger projects.

The results across real multi-day software projects cover team adaptation patterns, milestone completion rates, cost efficiency, and code quality. The verification phase — running between every execution cycle — catches defects that would otherwise compound across milestones. For any team that has watched a one-shot coding agent confidently build the wrong thing for three hours without feedback, the milestone-driven checkpoint architecture of TheBotCompany is a direct architectural response.

Read the full article at arXiv →