Your AI coding assistant is brilliant inside a single repo. Drop it into a DevOps workspace of a dozen and watch it fall apart.
It skims half of one repo and half of another, forgets which ones are read-only, blends their conventions, and spends most of its context window just trying to remember the rules. You ask one cross-cutting question and get a confident, half-wrong answer stitched together from the wrong files. The harder problem isn't the model, it's that you handed one brain a dozen jobs at once.
There's a fix, and it mirrors how good teams already split the work: give each repository its own specialised agent, and let one orchestrator route the work and merge the answers.
That's it. The rest of this post is the why and the how: the one constraint that quietly dictates the whole design, copy-pasteable starter agents you can drop in today, and the failure modes to avoid. Examples use Claude Code subagents, but the idea ports to any agent runtime with per-agent prompts and tool scoping.
TL;DR
