The Chief of Staff pattern: a coordinating session that never writes code and re-runs every claim
A 2026-09-19 writeup describes splitting Claude Code work into one long-lived coordinator and disposable executing sessions spawned through cmux (`cmux workspace create --name ... --command 'claude "Read docs/briefs/current.md and do exactly what it says."'`), with all state in a Plan Desk MCP board rather than conversation context. The eight-step loop pulls an unblocked task, runs the verifier first as a RED GATE that must fail, delegates, then re-executes the claimed commands and reads diffs line by line instead of transcripts. Two mechanics are concrete enough to steal today: verify a spawned session actually started by checking process timestamps, and use `git commit -- <paths>` in shared repos so concurrent sessions cannot commit each other's staged work.
Source
↳ Follow the thread