Claude Code Limits Draining Faster? What the Evidence Shows

If your Claude Code weekly limit is running out by Wednesday on a workflow that used to last the week, you are not imagining a pattern: search interest in "anthropic claude code limits" is up about 650% in the past week on Google Trends, and the Claude Code issue tracker has a cluster of reports dated from mid-October. What nobody has yet is a confirmed cause. This post separates what has been measured from what is anecdote, and gives you a ten-minute check to run on your own account.

What the primary sources actually say#

Anthropic's own help article on the Agent SDK says that when you are signed in with your Claude plan, the Agent SDK and claude -p still draw from your subscription limits. It says nothing about those calls being weighted differently from interactive use. That silence is the center of the most rigorous report so far.

On September 25 a user opened claude-code issue 97074 with a controlled A/B test on Claude Code 2.1.282 using Opus. Same work, same model, same effort, run once headless (claude -p, recorded as entrypoint: "sdk-cli") and once in the interactive terminal UI (entrypoint: "cli"). The reporter's numbers:

Nearly identical token spend, but the headless run consumed roughly 1.8x more of the five-hour window. A follow-up through a local logging proxy found the same gap, and other commenters reproduced it with their own logs. A later controlled run (with prompt caching disabled) measured about 1.32x for sdk-ts against the interactive UI, and about 1.14x when the same claude -p launch simply carried a custom CLAUDE_CODE_ENTRYPOINT label. A commenter who tested a cache-read-heavy workload saw little difference, so the gap is not universal.

The thread also notes what differs on the wire: the entrypoint value in the billing header and user agent, and one beta flag only the interactive client sends. That is observation, not proof of intent. As of November 4 the issue is open with no assignee, and the maintainers tagged in it had not answered in the comments I read.

The practical reach is wide. T3 Code's lead maintainer wrote in their tracking issue that Claude's five-hour limit drains about 1.7x faster in T3 Code than in the CLI because it runs on the Agent SDK, called it a bug on Anthropic's side, and closed the issue on November 2 after labeling T3 sessions with their own entrypoint. Our T3 Code write-up covers the Agent SDK limit caveat.

The separate mid-October weekly drain#

The second thread is different and weaker. In issue 105621, opened October 28, a Max user on the Windows desktop app reports weekly limits draining much faster since mid-October on an unchanged workflow, and others add similar reports across Pro, Max and the renamed Ultra plan. Issue 105240 describes a Max 5x account at 94% weekly usage in under 48 hours, with Anthropic Support reportedly attributing all of it to Claude Code.

Read the data carefully, though. One commenter in 105621 posted measured numbers: a single Opus 5.5 request that used 26% of a five-hour session, with about 5 million cache-read tokens across 48 model calls. Another used ccusage to show local token volume rising from late October while their weekly percentage per day stayed low. A third commenter retracted their claim after finding that 45% of their weekly usage was Cowork, not Claude Code. The reports are real and consistent in direction, but they mix plans, surfaces, models and workloads, and none proves a metering change.

Who wins and who loses#

Interactive users on the CLI look least exposed to the headless gap. Anyone running agent fleets, CI jobs, orchestrators or third-party front ends on a subscription is exposed, because those typically run through claude -p or the Agent SDK. That is the population our Agent SDK credit meter analysis covers, where programmatic usage is split from chat usage.

Anthropic's own packaging points the same way. Max, Ultra and Team plans now include monthly API credits that cover claude -p and the Agent SDK when you run them with an API key from a linked Console organization. If your automation burns subscription limits 1.1x to 2x or more faster than you budgeted, moving it onto API-key billing makes the cost explicit instead of hidden in a percentage bar.

What to do Monday#

1. Find your entrypoint. In recent Claude Code versions the transcript JSONL files under your Claude config directory record an entrypoint field per session. Count how many sessions are sdk-cli or sdk-ts versus cli. If most of your heavy work is headless, you have a candidate explanation.
2. Split the usage page. The account usage view separates Claude Code from Cowork and chat. One of the mid-October reporters found their own spike was Cowork.
3. Check cache behavior. Heavy cache-read sessions with long contexts consume quickly: the 26% single-request report above had about 156k tokens of context re-read across 48 calls. Our usage limits playbook covers context hygiene, and what parallel Claude agents cost shows how fan-out multiplies it.
4. Measure before and after. Note the weekly percentage, run one fixed task, note it again. One point of the meter is coarse, so repeat the task a few times before drawing a conclusion.
5. Do not rely on relabeling CLAUDE_CODE_ENTRYPOINT as a fix. Tools including xMatrix and a proxy project ship it, but their own maintainers asked Anthropic in the thread whether it is acceptable and said they would revert if not. Unapproved workaround, your account.

What people are actually saying#

Reddit's r/ClaudeAI has run several threads this week. One asks what is happening with limits and a Max 20x thread reports a week's allowance going in days. In the thread on the Ultra rename, commenters say the weekly cap was always the real constraint and that removing the five-hour window just lets you hit the weekly wall faster. That matches the analysis in our Ultra plan post. The counter-case lives in the GitHub threads themselves: at least one reporter retracted, and a cache-read-heavy tester saw little headless penalty. Treat Reddit as sentiment, not measurement.

Bottom line#

Verified: headless and Agent SDK traffic has been measured by multiple people as costing more plan window per token than the interactive CLI, by about 1.1x to 2.9x depending on workload (one uncontrolled report went the other way), and Anthropic's help article does not document a different weighting. Unverified: whether that is intentional, and whether it explains the broader mid-October weekly drain. If you run agents on a subscription, measure your entrypoint split this week and decide whether API billing is cleaner.

Continue Reading#

• Claude Code Usage Limits Playbook - how to stretch a window without changing models
• Claude Agent SDK Credits End the Subscription Arbitrage - why programmatic usage keeps getting separated from chat
• Claude Ultra Plan: Max 20x Renamed - what changed on the plan page
• What Parallel Claude Agents Actually Cost - fan-out cost per task
• T3 Code and the Agent SDK limit caveat - a front end affected by the same metering

Sources#

• Anthropic Help Center - Use the Claude Agent SDK with your Claude plan
• anthropics/claude-code #97074 - headless claude -p uses more of the 5-hour window per token
• anthropics/claude-code #105621 - usage limits drain faster since mid-October 2026
• anthropics/claude-code #105240 - Max 5x weekly usage at 94% in under 48 hours
• pingdotgg/t3code #24649 - Claude 5h limit drains faster in T3 Code than the CLI
• r/ClaudeAI - What the hel is happening with limits
• r/ClaudeAI - Claude Max 20x weekly limit thread
• r/ClaudeAI - Anthropic renames Max5 and Max20