Technical insights into multi-agent orchestration, local protocols, and
developer-centric terminal workflows.
Route a codebase search to a subagent pinned to a cheap model and two things happen at once: the search itself costs a fifth as much, and only a hundredth of it ever reaches the window where your expensive model is about to think.
The agent is an agreeable judge of done and the harness is a blind one. Two brakes, a third exit state, and the one night a $1.75 bill hides a lie.
A 20-issue Sentry triage sweep run inline leaves 21,000 tokens of tool exhaust in the main thread. Dispatched to a subagent under a three-line return contract, it leaves 60. The ratio holds at every cadence.
The GitHub MCP server that leaked private repo names in May 2025 had no malicious code in it. The token's authority was ambient, good for every repo you can see. Scope it to the task and the blast radius drops 12x.
When the window fills, auto-compaction writes a faithful summary and a handoff file writes an edited one. Both can be 200 tokens; next session they are 5,000 tokens apart, and the whole gap is one line saying what was ruled out.
A raw token passthrough hands an injected agent all 34 endpoints of your billing API, five of them destructive. Hold the token server-side and expose three curated verbs instead: one bounded write, capped at $500 a call and logged.
A relay of fresh sessions inherits every earlier decision through the plan file's checkboxes. But the model that ticks a box has every incentive to believe its own diff. An unaudited checklist is a bet, and this is the arithmetic that prices it.
An event can fire a headless agent run as reliably as a hook fires inside a session. But wiring the event only removes the human who had to remember to ask. The one who caught bad output has to be rebuilt as code too: rules for what a careful review would do, guards for what it would never let happen unattended.
A model has one procedure for turning tool bytes into a sentence, so a clean success and a swallowed failure read the same. On 12 refund calls, narration confirms 3 that never happened; a validated output schema confirms zero.
A suite thorough enough to catch a real regression is too slow and noisy to gate every PR. Split the same 50 cases into a 32-case deterministic gate and an 18-case nightly judge sweep, and a team merging 8 PRs a day gets 156 minutes of blocked PR time back every week - without dropping a single case.