AgentComparison
Usage guide · Anthropic documentation, attributed

Claude Code usage limits: how to stretch them

Running out of Claude Code usage early in the day is a common complaint. Anthropic's help article Models, usage, and limits in Claude Code (dated 15 April 2026) explains how usage is metered and what drives it. This guide summarises that article and keeps Anthropic's advice separate from our own notes. We have not run measurements ourselves, and Anthropic says model names and availability change, so treat /model in your own account as the source of truth.

Limits and plan figures rechecked 1 November 2026; metering article dated 15 April 2026Anthropic Help CenterNo hands-on test

How usage is metered

You signed in withWhat you get, per AnthropicWhat running out looks like
A Claude Enterprise seatA pool of usage included in your organisation's plan, reset on a rolling window.A "limit reached, resets at time" message.
An API key (Console, Bedrock, Vertex or Microsoft Foundry)Pay-as-you-go, billed per token to that account.No hard stop. The account is charged for what it uses.

The same article says /cost shows your running spend for the session when you use an API key. It does not describe Pro or Max plan limits on this page. Anthropic covers those in a separate help article, Use Claude Code with your Pro or Max plan. Our Claude Code record lists the plans and prices as published.

What uses tokens

Anthropic says every turn sends the conversation so far, your project context (CLAUDE.md and files Claude has read) and your new prompt. The conversation grows fastest, so a long session carries everything it has read and changed on every later message. Anthropic says this is where both cost and context limits come from.

Five habits Anthropic recommends

  1. Clear between tasks. Run /clear when you switch to an unrelated task. Anthropic calls it the most effective lever for quality and cost. It cannot be undone, and CLAUDE.md and project files stay.
  2. Match the model to the job. Anthropic describes Sonnet as the default for most coding, Opus for harder problems at meaningfully more quota, and Haiku for quick mechanical work. A common pattern is to plan with Opus and execute with Sonnet, which /model opusplan does.
  3. Point at files instead of pasting them. Pasted text stays in context for the session. Anthropic notes that the @ prefix injects the whole file plus its CLAUDE.md tree, so use a bare path when saving tokens, and trim logs to the relevant 20 or 30 lines.
  4. Keep CLAUDE.md lean. It is added to every turn. Anthropic suggests adding a note only the second time you correct the same thing, keeping the file under roughly 200 lines, and pruning stale notes every few weeks.
  5. Ask for a plan before big changes. For anything touching more than two or three files, use Plan Mode or ask for the list of files and edits first, correct it, then execute.

Plan limits: five-hour and weekly windows

Anthropic’s companion article, Use Claude Code with your Pro or Max plan (read 1 November 2026), describes the subscription limits:

Background agents: the reported status-line cost transcript tools can miss

One overhead the help articles above do not mention comes from community reports, not from Anthropic: users report that while a background agent is working, Claude Code sends that agent's whole transcript to the model roughly every 30 seconds and asks for a 3-to-5-word status line for the agents panel. We have not reproduced this, and Anthropic has not confirmed the behaviour in the sources we read; the reports describe calls labelled agent_summary that are marked to skip the transcript, so the reporters say the transcript-reading cost tools they used did not count them - they measured through OTel exports or a proxy in front of Claude Code instead (GitHub issue anthropics/claude-code#86879 and the Hacker News discussion, both read 2 November 2026).

How much does it cost? Community measurements vary widely, and none is ours: the issue reporter measured 22.7% of requests and about 18% of weighted tokens in one subagent-heavy session; another user reported about 14% of requests and 10% of spend across 129 sessions, peaking at 24% in a 40-agent session; one Hacker News commenter put their organisation near 3%; a widely shared gist put one user's weekly figure at 16.4% of spend by Claude Code's own estimate. These reports come from different setups - single heavy sessions, a 129-session history, one organisation's total - and none of the sources establishes what explains the differences between them.

Two cautions. First, there is no documented off switch: as of version 2.1.312 users report no supported way to disable these calls, an undocumented setting name exists in recent builds with unconfirmed behaviour, and the two-month-old issue had no maintainer reply when we read it on 2 November 2026. Second, a claim circulating on Reddit that Anthropic replied on Hacker News with a ~2% average and shipped a fix in version 2.1.311 did not verify when we checked - we found no such reply in the thread and no such entry in the official changelog. Whether these calls also draw on Pro and Max subscription allowances, rather than only API-billed spend, is not stated in the sources we read.

Practical takeaway: if you run background agents on API billing, the reporters' shared advice is to measure with an OTel export or a proxy rather than transcript-based tools. What the overhead means for your own usage is something only your own measurement can answer.

Context window versus usage limit

Our notes

These are our reading of the article, not Anthropic's claims. The advice is about keeping what is resent each turn small, which is why clearing, short context files and plans help. We have not measured how much each habit saves. If you are choosing between coding agents on cost, see Replit Agent vs Claude Code vs Devin and Devin pricing explained.

Source: Anthropic Help Center, Models, usage, and limits in Claude Code. Spot a change? Tell us.

Plan limits as Anthropic documents them (31 October 2026)

Anthropic's current pricing page lists four individual plans. Free has limited usage every 5 hours and every week. Pro is 1x on both windows and includes Claude Code. Max is 5x Pro on both the 5-hour and weekly windows and includes $100 a month in Claude Platform API credits. Ultra removes the 5-hour limit for verified accounts, gives 10x Pro on the weekly window, and includes $200 a month in API credits. On the Team plan, Standard seats get 1.25x Pro per session and Premium seats 6.25x Pro per session, both with a weekly limit across all models; Anthropic publishes weekly multiples for the individual plans (Pro 1x, Max 5x, Ultra 10x) but only per-session multiples for Team seats, so a Team-seat weekly figure cannot be compared with an individual plan's weekly multiple from the documentation. Team limits are per-member, not shared across the organisation.

A naming note for readers coming from older articles: Anthropic renamed its top individual tiers in 2026, so pieces written about "Max 5x" or "Max 20x" plans describe the tiers now named Max and Ultra. The current Ultra allowance is 10x Pro weekly, not the 20x the old name implied.

Other documented points: usage on claude.ai, Claude Code and Claude Desktop counts toward the same allowance, so heavy app use competes with Claude Code time. Fable has a separate weekly limit on some plans. Limit resets exist but are given occasionally to eligible plans - they cannot be bought on demand. Sources: claude.com/pricing (read 31 October 2026, GBP view) and Anthropic support articles on usage limits, the Team plan, monthly API credits and limit resets.