{"slug": "do-subagents-burn-your-claude-code-limit-faster", "title": "Do subagents burn your Claude Code limit faster?", "summary": "A developer measured subagent token costs on a single Claude Code account over two days (23–25 October), finding that each subagent model call consumes roughly 0.07% of the 5-hour limit — about the same as a main-thread call. Subagents drain the limit through call volume rather than per-call cost: a typical subagent used about 1.9% of a 5-hour window, while the largest (86 calls) used 10.1%, and the costliest tenth of subagents accounted for 29% of all subagent usage. The findings were published alongside limitcast, a local-only CLI tool that forecasts when Claude Code, Codex and Grok usage limits will run out.", "body_md": "Subagents are the usual suspect when a Claude Code limit runs out early. I measured what they actually cost on my account, using the same fit as in [How many tokens is 1% of your Claude Code limit?](https://limitcast.dev/blog/tokens-per-percent/)\n\n**Per model call, no.** A subagent call cost about the same share of my 5-hour limit as a main-thread call: roughly 0.07%. Subagents burn the limit because of how many calls they make. A typical subagent cost about 2% of a 5-hour window, so five in parallel cost about 10%.\n\nOver two days (23–25 October), on one account:\n\n|  | Model calls | New tokens per call | Cached tokens per call | Limit per call | Share of the limit used | \n|---|---|---|---|---|---|\n| Main thread | 4,234 | 6.6k | 353k | 0.072% | ≈ 60% | \n| Subagents | 2,895 | 8.4k | 223k | 0.071% | ≈ 40% | \n\nThese two days end a few hours later than the ones in the first post, so its subagent share (42%) and this one (40%) differ slightly.\n\nThe two cancel out. The main thread re-reads a bigger context on every call (353k cached tokens against 223k), but cached tokens count about 1/67 as much as new ones. Each subagent writes its own context into the cache from scratch, so its calls carry more new tokens (8.4k against 6.6k), and new tokens are what move the meter.\n\nThe same two days had 93 subagents. Priced against the 5-hour limit:\n\n| Typical subagent (median) | 16 calls | ≈ 1.9% of a 5-hour window | \n| Average |  | ≈ 2.3% | \n| 1 in 10 cost more than |  | ≈ 4.1% | \n| Largest | 86 calls | ≈ 10.1% | \n\nThe costliest tenth of subagents used 29% of everything subagents used. Most subagents are cheap; a few long ones are not, and a batch of them started at once is what ends a window early.\n\n```\nnpm install -g limitcast\nlimitcast install      # records your limit readings from the status line\n# use Claude Code for a day or two, then:\nlimitcast results      # what moves your meter: new vs cached tokens\nlimitcast report       # Pro: tokens by day, project, model and session, and the subagent share\n```\n\nThe free version is local-only and never uses your Claude login.\n\n*Originally published at [limitcast.dev](https://limitcast.dev/blog/subagents/). limitcast is a local-only command-line tool that forecasts when your Claude Code, Codex and Grok usage limits run out.*", "url": "https://wpnews.pro/news/do-subagents-burn-your-claude-code-limit-faster", "canonical_source": "https://dev.to/samstull9007/do-subagents-burn-your-claude-code-limit-faster-4ke5", "published_at": "2026-10-27 18:27:09+00:00", "updated_at": "2026-10-27 18:42:58.977928+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "large-language-models", "ai-agents"], "entities": ["Claude Code", "limitcast", "Codex", "Grok", "Anthropic"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/do-subagents-burn-your-claude-code-limit-faster", "markdown": "https://wpnews.pro/news/do-subagents-burn-your-claude-code-limit-faster.md", "text": "https://wpnews.pro/news/do-subagents-burn-your-claude-code-limit-faster.txt", "jsonld": "https://wpnews.pro/news/do-subagents-burn-your-claude-code-limit-faster.jsonld"}}