Agent Tile BlogRunning a fleet of AI coding agents, well.

The Hidden Cost of Context-Switching Between AI Coding Agents

· workflow, productivity, fleet

Running four agents in parallel looks like 4× throughput. In practice, the gain is smaller than it should be, and the reason has a name: context-switching cost. Every time you turn to a session, you spend a few seconds reloading "what was this one doing, and what was it waiting for?" Multiply that by dozens of switches an hour and the tax is real.

Where the cost actually comes from

  • State reconstruction. You look at a wall of output and rebuild the mental model of that task from scratch.
  • "Who's waiting?" scanning. With several agents, the hard question isn't doing the work — it's noticing which agent has stopped and needs your input. That scan is pure overhead.
  • Wrong-window actions. Under switching pressure, you type into the session you thought was active. Undoing that costs far more than the switch itself.

How to cut it

  1. Externalize state so you don't rebuild it. Labels, folders, and a visible status per session mean the answer is on screen, not in your head.
  2. Get pushed, don't poll. A notification hook that pings you when an agent finishes removes the constant "is it done yet?" scanning. Ten lines of config recovers more time than faster typing ever will.
  3. Make selection explicit. When you send the same instruction to several agents, you want to see which ones are selected before you send — a preview, not a guess. See broadcasting one command to many sessions.

Design for the scan, not the typing

The biggest wins come from making "which agent is waiting on me?" a glance instead of a search. That's the layer Agent Tile is built around — every session as a labeled tile with project and folder visible at once — but the principle applies to any tooling: optimize for state visibility first.

Takeaway

Parallel agents only pay off if you keep context-switching cost low. Externalize state, get notified instead of polling, and make selection explicit. The throughput was never limited by the model — it's limited by how fast you can re-orient.

Agent Tile
Practical guides for running many Claude Code sessions in parallel on macOS — orchestration, review workflows, and staying sane with a fleet of AI coding agents.
Get Agent Tile — full source, $10 once →
Also from TechAthletes
  • IT-QA — Technical Q&A with AI-assisted answers and point bounties — for the questions that come up while you're running a fleet.