
What happened
A freelance engineer measured his Claude Code setup and found 4 of 6 subagent definitions left the model field blank, inheriting the parent's opus model; a subagent that only echoed 'X' once used 101,418 tokens, about 90,000 of it CLAUDE.md.
Why it matters
The cost of delegating came mostly from the shared context every subagent reloads, not from the task itself — and the improvement loop that should have run every 4 hours had already missed 8 straight cycles on usage_limit.
What to watch
Whether specifying a model per role actually lowers usage limits hinges on whether the parent and subagent contexts are truly separated; the engineer measured total consumption as roughly round trips × (CLAUDE.md + foundation + work content), and three of Claude's call paths remained unspecified at the start.
WHO IT HITSEngineers running Claude Code on a flat-rate plan are the ones affected: leaving model fields blank in .claude/agents/*.md lets every subagent run on the parent's most expensive model, so the usage cap arrives before the roles that genuinely need opus get their turn.
Summaries like this, in your inbox every morning.
The engineer runs a blog and an X account on Claude Code from GitHub Actions on a VPS, calling claude -p on a schedule. The audit began when a review pointed out that his model selection was not actually differentiated. He first counted every path that calls Claude — an improvement loop every 4 hours, article writing twice a week, research, chat, and a smoke test — and found three of them left the model unspecified. The subagent definitions had the same problem: of six, only two named a model.
The immediate symptom was practical rather than theoretical. Records from the improvement loop's stop-reason file showed eight consecutive runs from September 20 and 21 all hitting usage_limit, leaving the loop stuck for two days. The engineer is careful not to assert that opus alone caused this, since the flat-rate quota is shared with human sessions and other paths — but he notes that running cheap roles on an expensive model does bring the cap closer before the roles that truly need opus get their turn.
He also documents a hypothesis he nearly reported without testing: that Task was missing from --allowedTools and subagents were structurally impossible to call. A measurement showed subagents spawned and completed with zero permission denials, so the real problem was that nobody was calling them, not that they couldn't be called. The stakes in the rest of the piece flow from that distinction — the fix is a prompt change, not a permissions redesign — and from his choice to keep article writing, public post writing, and the smoke test on opus while pushing no-judgment roles down to haiku.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Lauren Tan says she shipped about 2,000 pull requests a month to production on the SpaceX AI Grok Bot team

Reading one spec-index file of 803 lines on 2026年9月29日, an external program returned about 798 tokens against…

In a trial run, an agent set up .NET, built the core library, ran 34 unit tests and configured CI in about fiv…

KnowledgeSense said on September 30 that CodeSense, a Japanese-made AI agent, will ship within a few weeks, an…

Among respondents at companies with 1,001+ employees, 50.0% said AI is used company-wide, and 46.0% flagged AI…

Google published four design patterns from the top entries of its Google for Startups AI Agents Challenge, jud…
