The Hidden Cost of Building an AI Agent Better Than Claude Code
Everyone wants to build "the next Claude Code." A multi-agent system where a lead orchestrates a team of specialists, tasks flow through a kanban, reviewers gate quality, and humans sit back. On a ...

Source: DEV Community
Everyone wants to build "the next Claude Code." A multi-agent system where a lead orchestrates a team of specialists, tasks flow through a kanban, reviewers gate quality, and humans sit back. On a whiteboard it looks elegant. In production, it bleeds tokens. I spent some time profiling exactly where those tokens go in a realistic multi-agent setup — a lead, three teammates, ten tasks, full lifecycle. The result is uncomfortable: roughly 92% of the tokens in a session are not doing useful work. They are tool schemas and protocol text, repeated turn after turn, agent after agent. If you're thinking about building an agent framework on top of Claude, GPT, Gemini, or anything else, this is the tax nobody warns you about. Where the tokens actually go Here's the lifecycle cost for a modest run — three teammates working ten tasks end to end: Phase What's in it Tokens Provisioning Lead prompt + spawn instructions ~4,500 Teammate spawns Identity + protocol + workflow per member ~4,500 Member br