// HACKER NEWS — CYBERSECURITY
Orchestrating Claude Code Agents: The Chief of Staff Pattern
One session coordinates and verifies while others execute, with a durable board holding state. An orchestrator-worker loop for long-running Claude Code agents.
Long-horizon AI coding work fails less because agents cannot write code and more because their context is ephemeral and their self-reports are unreliable. The fix is organizational rather than technical: one session coordinates and verifies while separate sessions execute, a durable external board holds the state, and every claim is re-run before it is believed. The shape is already known as orchestrator-worker and coordinator-implementor-verifier. Chief of Staff is just what we call it. This covers the loop, the tooling that makes it practical, and the failure modes it exists to catch.
A single AI coding session works well for an hour and degrades after that. Three things go wrong.
Adding more agents does not fix this. It multiplies it. Now you have several unreliable reporters and no one reconciling them.
What fixes it is a division of labour borrowed from human organizations: someone whose job is not to do the work, but to know what is true.
This is the same discipline that separates a prototype from a shipped product. The generation step was never the bottleneck. The checking step is.
Chief of Staff is our name for an agent orchestration shape in which one long-lived session acts as coordinator, assigning work, verifying claims, and maintaining shared state, while separate short-lived sessions perform the implementation.
If you want the fastest mental model, think of it as an integration manager. In Git’s integration-manager workflow, contributors work in their own repositories and one maintainer pulls each change, tests it locally, and decides what lands in the reference repository. The coordinator does that job, for agent sessions instead of contributors.
The name is a metaphor we find useful. It is not an established term, and you should not have to recognize it. The shape underneath it is well known and has several real names.
They all say the same thing: one agent plans and checks, others do the work, and shared state lives outside any single context window. If you are looking for prior art, search those terms rather than this one.