Q Answer-format search page
How to route work across multiple AI agents
✦ AI editor's answer
Decide by handoff capability (can it append to the same work ledger — files, conventions, state?), not by model name. Split strong-reasoning vs fast-bulk by undo-cost.
Source: 4 notes from this publication + operator work logs
Source notes (4)
- Tooling2026-05-20
Mixing Claude, Codex and Gemini in one workspace — what 132K events revealed
81,764Claude events (61% of all)› Route 'hard-to-undo' work (design, review) to a stronger reasoning model; route bulk repetitive work to a fast cheap model.
- Tooling2026-05-25
26 hands — but one of them passed 1,333 messages
1,333Messages exchanged by a single deep session› Session count is the weaker signal; messages and tool-calls per session are the real automation depth.
- Tooling2026-05-23
95 hands shared one desk
95Sessions on one workspace, zero conflicts› When multiple agents share one folder, what prevents conflict is not the model — it's a shared work-ledger convention.
- Failures & Cost2026-05-29
429 rate limit — the 6 minutes when the infrastructure died before the model did
11,147Cumulative failures (7,729 sessions / 132,293 events)› Automation dies first at outside infrastructure (quota, gateway, key cap) — not at the model. Same model, same prompt can still die in 6 minutes. Bake that in as a baseline.
Related questions