Router-Worker Architecture Moves an AI Workbench From Session Firefighting to a Task Board
Task-level orchestration with event-derived state makes unattended parallel agents practical: a solo developer can hand scheduling to a Router and still keep acceptance authority. The constraint is that whichever Worker you scale has to be reliable enough to self-verify and recover, otherwise a Router just spreads errors across more sessions.
Human attention is the real limit in parallel AI pairing, not agent capability. The workbench operator caps usable parallel sessions at three; beyond that, a notification from one window gets dropped when an urgent bug pulls attention elsewhere. The fix is to manage tasks rather than sessions. A task becomes a persistent canvas that outlives any Claude Code or Codex window, holding specs, design screens, reports, and acceptance records. Task status is not stored; it's derived from a set of events the agent reports at the end of each round via canvas-agents report, such as ready, blocked, or dropped. Seven states run from unplanned to done, and a task is awaiting review whenever any of its windows is blocked waiting for human input.
The Router layer sits above tasks. A resident agent, called the Spirit Steward, receives requests from the chat window and from external triggers: GitHub issues, Feishu groups, and soon Jira. It triages, creates work orders, and dispatches sessions, but never writes code itself. It follows the Super Agent rule that state does not live in the conversation, so closing a window or compressing context never loses task progress. A human remains the only one who can mark a task done. The author argues quality must come before scale: each Worker needs to be able to define, verify, and recover on its own, and only then does a Router multiply concurrency without multiplying mistakes.
Keeping state out of the conversation and out of storage is what makes the difference: task identity survives any session refactor. The event-log approach is a simple, practical substitute for a dedicated state machine.
A Router that is forbidden from doing real work creates a clear control boundary: the human keeps the only acceptance privilege, which is what makes delegating scheduling to an agent safe.
The quality-first rule means concurrency is not a free win: you need Workers that can define, verify, and recover on their own, or a Router will just multiply broken outputs across many sessions.