# Orchestration How CodeHerder runs many coding agents as one system: staffing, coordination, and the failure modes a lone agent never hits. Source: https://codeherder.com/blog/topics/orchestration/ Topic One agent is a tool. A fleet of them needs a plan for who does what, and when. Orchestration is the work of turning several coding agents into one dependable team, not several unsupervised tools. It covers how a task reaches the right agent, and how one agent's output feeds the next stage. It also covers what happens when an agent stalls, or gets a task wrong. This matters because a single agent's mistakes are easy to spot. A fleet's mistakes hide in the handoffs instead. Two agents edit the same file, or a task waits on a device that never checks in. CodeHerder makes those handoffs a solved problem instead of a support ticket. Read this hub if you run more than one agent at a time, or if you plan to. The posts below cover real coordination failures we hit while building the herd, and how the workflow closes each one. [Request access →](https://codeherder.com/get-started/#request-access) September 12, 2026 · 8 min read ## [We asked our agents what slowed them down](https://codeherder.com/blog/we-asked-our-agents-what-slowed-them-down/) Our first Agent Experience survey put five questions to every code-stage agent for a day. 84 of 85 answered. Here is how it works and what the herd told us. For everyone - [observability](https://codeherder.com/blog/topics/observability/) - [workflow](https://codeherder.com/blog/topics/workflow/) - [orchestration](https://codeherder.com/blog/topics/orchestration/) August 24, 2026 · 7 min read ## [We moved our production database from SQLite to PostgreSQL without slowing down](https://codeherder.com/blog/database-migration-at-full-speed/) A 33-minute cutover window and 99 of 99 tables verified, shipped while the same codebase absorbed 637 merges and a dozen other initiatives. For everyone - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [workflow](https://codeherder.com/blog/topics/workflow/) - [quality](https://codeherder.com/blog/topics/quality/) August 17, 2026 · 6 min read ## [Collide, forget, repeat: the three ways parallel agents get out of sync](https://codeherder.com/blog/collide-forget-repeat/) Run enough clean-context coding agents in parallel and three problems appear: they collide, forget, and repeat house rules. Here's how CodeHerder fixes that. For everyone - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [workflow](https://codeherder.com/blog/topics/workflow/) August 5, 2026 · 8 min read ## [The most expensive line in your agent config is the model name](https://codeherder.com/blog/reasoning-model-is-the-cost-lever/) Agent cost doesn't track codebase size. Swapping our judgment stage's reasoning model moved a story's cost 2.4x, and its lead time nearly 3x. For everyone - [cost](https://codeherder.com/blog/topics/cost/) - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [observability](https://codeherder.com/blog/topics/observability/) August 1, 2026 · 10 min read ## [Give your agents their own machine: what CPU contention costs a parallel herd](https://codeherder.com/blog/dedicated-hardware-for-concurrent-agents/) Parallel Claude Code sessions need dedicated hardware. Load-matched data puts one machine 40% ahead, and a spot m9g.xlarge holds ten sessions. For everyone - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [cost](https://codeherder.com/blog/topics/cost/) July 25, 2026 · 14 min read ## [10 things we learned running 100 billion tokens through a herd of AI agents](https://codeherder.com/blog/100-billion-tokens/) Two months of CodeHerder data: 1.2 million agent API calls, 110 billion tokens, 5,742 finished tasks, and a median story costing $7.54, done in 50 minutes. For everyone - [cost](https://codeherder.com/blog/topics/cost/) - [observability](https://codeherder.com/blog/topics/observability/) - [orchestration](https://codeherder.com/blog/topics/orchestration/) July 19, 2026 · 5 min read ## [Can you trust AI-generated code? A practical guide to reviewing agent work at scale](https://codeherder.com/blog/trusting-ai-generated-code/) The real question isn't whether AI agents can write code. It's whether you can trust code you didn't watch get written. Here's how gates make that answer yes. For everyone - [quality](https://codeherder.com/blog/topics/quality/) - [orchestration](https://codeherder.com/blog/topics/orchestration/) July 15, 2026 · 9 min read ## [How to run a team of AI coding agents: a practical guide to orchestration](https://codeherder.com/blog/how-to-orchestrate-ai-coding-agents/) Going from one AI coding agent to a coordinated herd that ships reviewed, cost-bounded work: the problems that show up, and the operating model that fixes them. For everyone - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [workflow](https://codeherder.com/blog/topics/workflow/) May 18, 2026 · 3 min read ## [One agent is a tool; a herd needs a shepherd](https://codeherder.com/blog/one-agent-is-a-tool-a-herd-needs-a-shepherd/) A single coding agent is easy to supervise. Ten of them is a coordination problem nobody's tool was built to solve. For everyone - [orchestration](https://codeherder.com/blog/topics/orchestration/) - [workflow](https://codeherder.com/blog/topics/workflow/) [← All topics](https://codeherder.com/blog/topics/) [All insights](https://codeherder.com/blog/)