Claude limit reached: what to do next

Which Claude limit did you hit

A Claude limit reached message names the window you are waiting on, and that window decides what you can do next. On Pro and Max, session and general weekly limits cover every model at once, so switching models does not give your access back. Ultra's general weekly limit also covers every model at once. A limit that names one model is the exception: change models and you keep working while that one model stays blocked. Anthropic also advises Enterprise seat users who reach a usage limit to try a lighter model with /model.

Claude Code prints the window and its reset time in the same line:

You've hit your session limit · resets 3:45pm
You've hit your weekly limit · resets Mon 12:00am
You've hit your Opus limit · resets 3:45pm

The session window is a rolling five hours. Weekly windows reset at a fixed time each week that is assigned to your account, so the day and the hour stay the same from one week to the next. A Pro plan has the five hour session window plus one weekly limit that applies across all models. A Max plan adds a second weekly limit that applies to one model family on its own. Ultra also has a general weekly limit and a separate weekly Fable limit, but verified Ultra accounts have no five hour limit. Accounts not yet verified have a temporary limit until Anthropic verifies them automatically. The ceilings themselves live in the full breakdown of Claude usage limits. This page starts where that one ends.

Here is the part that catches people out. Where a session limit applies, every request counts against the session window and the weekly window at the same time, so one heavy afternoon can empty the weekly allowance while the five hour window still has room in it. Read the reset time before you plan the rest of your day. A reset at 3:45pm is a coffee break. A reset on Monday at midnight is not.

Read the meter before you guess

On claude.ai, open Settings and then Usage. Progress bars show how much of the five hour session window and each weekly window you have spent, so you can see which one is empty instead of guessing. Verified Ultra accounts have no Current session bar.

In Claude Code, run /usage. It shows the same plan bars plus a breakdown of where recent usage went, attributed to skills, subagents, plugins and individual MCP (model context protocol) servers as a percentage of the total. Press d for the last 24 hours and w for the last 7 days. It also flags any pattern that accounts for 10% or more of recent usage, and the two you will see most are long context and cache misses.

Two caveats. The breakdown is computed from session history stored on that machine, so work you did on another laptop or on claude.ai is missing from it, even though it drew on the same allowance, because Claude Code and your claude.ai chats share one subscription window. And the dollar figure in the Session block at the top is an estimate intended for API (application programming interface) users. Claude Code prices it at standard list rates unless an administrator has set a modelPricing table in your organization's managed settings, in which case it uses those contracted rates and the Total cost line says at your organization's configured rates. Either way it is not your bill when you are on a subscription.

Does switching to a smaller model help?

Yes, when the message names a model, and Anthropic also recommends trying it for Enterprise seat users who reach a usage limit. After You've hit your Opus limit, run /model, pick Sonnet or Haiku, and the session carries on with everything in context. On Pro, Max and Ultra, after You've hit your session limit or You've hit your weekly limit, /model does not restore the shared allowance. When it is Opus alone that is blocked, what a spent weekly Opus allowance means covers when Opus comes back and whether usage credits or a move to Max bring it back sooner.

The switch is worth far more before you hit the wall than after. Sonnet handles most coding work at a fraction of the Opus rate, so leaving Opus as your default is one of the two habits behind most surprise usage. The other is a session that never gets cleared. Give mechanical edits and log triage to Haiku, and keep Opus for the design decision you are genuinely stuck on. Choosing between Opus, Sonnet and Haiku goes through where each one earns its price.

Stop paying for context you stopped using

Claude Code sends your whole conversation with every request, and each time Claude uses a tool it sends another request carrying that batch of tool results. Prompt caching means the history is re-read at the cached rate instead of the full input rate, which makes it cheaper, not free. So a one line question in a session you have had open since morning still draws usage for the entire conversation.

/context
/clear
/compact Focus on the failing tests and the files we changed

/clear costs nothing, because it throws the context away rather than reading it. /compact has to read the conversation it summarizes, so compacting a very large context is itself a large request. Use /clear when you move to unrelated work, and /compact only when you are mid task and need the thread to survive. Run /rename before clearing so you can find the session again with /resume.

Cache lifetime matters more than most people expect. On a subscription, while you are inside your plan's included usage, the main conversation's cache lives for an hour. Subagents and most other background requests get five minutes even on a subscription. The main conversation drops to five minutes once you are drawing on usage credits, and five minutes is also the default on an API key. The promptCacheTtl and subagentPromptCacheTtl settings override those defaults if you want a different lifetime. Your first message after a long lunch misses the cache, so the whole context is processed again and written back into the cache. At API list rates a cache write costs more than plain input, 1.25 times the base input price for a five minute cache and 2 times for a one hour cache, which is why usage often jumps for no visible reason. Where prompt caching pays for itself covers the arithmetic.

Three more levers sit in the same place. /mcp lists your configured servers so you can switch off the ones this task does not need. A long CLAUDE.md loads at session start whether the work needs it or not, so move specialized instructions into skills, which load only when invoked. And extended thinking is billed as output tokens, which is the expensive half, so lower it with /effort, turn it off in /config on a model that allows it, or set MAX_THINKING_TOKENS=8000 on a model with a fixed thinking budget. Claude Code cannot switch thinking off on Opus 5.5, Sonnet 5.5, Haiku 5.5 or the Fable models, so on those /effort is the lever. That is a Claude Code rule rather than a model one: on the API, Haiku 5.5 accepts thinking turned off at high effort or below, and Sonnet 5.5 can drop its up-front thinking with the between_tools setting, while Opus 5.5 and the Fable models reject thinking off everywhere.

Split the job so it fits inside one window

Press Shift+Tab to cycle into plan mode before a large change. Claude explores the codebase and proposes an approach for your approval, and a wrong direction caught there costs one plan instead of two hours of edits plus the rework.

Delegate loud operations to subagents. Running a test suite or reading a 10,000 line log inside a subagent keeps the raw output in that subagent's context, and only the summary returns to your main conversation.

Press Escape the moment Claude heads somewhere wrong. /rewind restores both the conversation and the code to an earlier checkpoint, so you are not paying to unpick work you never wanted.

Should you buy usage credits or use the API?

Usage credits let a Pro, Max or Ultra account keep working past the plan allowance, billed at standard API rates. Turn them on under Settings and then Usage on claude.ai with a payment method attached, then add funds, because credits are prepaid and only cover usage once you have bought some. You can also run /usage-credits in Claude Code, which opens your billing settings in the browser. Credits apply to Claude conversations and to Claude Code terminal usage, and the cap on them is a monthly spend limit you set yourself with Adjust limit, or remove with Set to unlimited. The command needs a subscription login, so it is not available when you authenticate with an API key. On the free plan credits are not offered at all, so the first move is Pro at $20 a month, and what Pro adds and where its limits stop you sets out how far that gets you. If you are topping up with credits most weeks, a bigger allowance is usually the cheaper habit. The gap between $100 Max and $200 Ultra is mainly the allowance: Max gives 5x Pro usage every five hours and every week, while Ultra gives 10x Pro usage every week with no five hour limit for verified accounts. Both are monthly web prices, with mobile pricing varying, and both plans offer monthly billing only. They also include different monthly Claude Platform API credits, $100 on Max and $200 on Ultra, which do not raise your limits in Claude or Claude Code.

The other route is a plain API key from the Claude Console, billed per token with no session or weekly window at all. One trap comes with it: a stray ANTHROPIC_API_KEY in your environment can take over from your subscription. In an interactive session Claude Code asks once whether to use the key and remembers your answer, so a quick yes from months ago is easy to forget, and the Use custom API key toggle in /config changes it back. In a non-interactive -p run it asks nothing and uses the key whenever it is set. You find out from the bill, or from this:

API Error: Request rejected (429) · this may be a temporary capacity issue. If it persists, check https://status.claude.com.

That 429 is the rate limit on the key, not on your plan. Run /status and confirm the active credential is the one you meant to use. When a login and an API key are both configured, /status marks the one that is not in use.

What does an afternoon on the API cost?

The worked example below is one afternoon of agent-style coding: 200,000 uncached input tokens, 1.8 million cache reads, and 150,000 output tokens. Prices are Anthropic list rates as of October 2026. Every one of those rates is quoted per million tokens, so if that unit still feels abstract, what a million tokens is actually worth turns it into an amount of reading and writing you can picture.

[
  {
    "label": "Opus 5",
    "input_usd_per_mtok": 5,
    "cache_read_usd_per_mtok": 0.5,
    "output_usd_per_mtok": 25,
    "afternoon_usd": 5.65
  },
  {
    "label": "Sonnet 5",
    "input_usd_per_mtok": 2,
    "cache_read_usd_per_mtok": 0.2,
    "output_usd_per_mtok": 10,
    "afternoon_usd": 2.26
  },
  {
    "label": "Haiku 4.5",
    "input_usd_per_mtok": 1,
    "cache_read_usd_per_mtok": 0.1,
    "output_usd_per_mtok": 5,
    "afternoon_usd": 1.13
  }
]

The same afternoon costs $5.65 on Opus 5 and $1.13 on Haiku 4.5. Output is what moves the total: at $25 per million tokens on Opus 5 against $5 on Haiku 4.5, the 150,000 tokens Claude writes cost more than the 2 million tokens it reads. That is why lowering the thinking budget saves more than trimming files. If the question is which provider to pay rather than which model to run, three jobs costed on both the Claude and ChatGPT APIs shows where each bill comes out ahead.

One date that passed without a change. Sonnet 5 launched at $2 and $10 per million input and output tokens, announced as introductory pricing through 31 August 2026, with a move to $3 and $15 scheduled for 1 September 2026. Anthropic cancelled that increase and made $2 and $10 the standard price, so the same afternoon still costs $2.26 on Sonnet 5.

The newest models bring the same afternoon down again. Opus 5.5, released on 22 September 2026, lists at $4 input and $20 output with cache reads at 5% of the input rate, which puts the afternoon at $4.16. Sonnet 5.5 keeps the $2 and $10 rates but halves cache reads to $0.10, for $2.08. Haiku 5.5 starts at $0.10 and $0.50, and charges five times that on any request whose prompt runs past 100,000 tokens, so its total depends on how large your context grows.

For scale, Anthropic's own documentation puts average Claude Code spend across enterprise deployments near $13 per developer per active day, and under $30 per active day for 90% of users, as of October 2026. Per token billing is not automatically cheaper than a subscription. It wins when your load is spiky, because quiet days cost nothing, and it loses when you work every day. The API against a subscription, compared with real numbers has the crossover.

Run the long job on a VPS overnight

Some jobs do not need you watching: a large refactor, a test migration, a documentation sweep. Those jobs also do not need your subscription window. Put them on a VPS (virtual private server) with an API key and they draw on per token billing while your plan allowance sits untouched for tomorrow's interactive work. A cloud session runs Claude Code on Anthropic's servers by default with no server for you to manage, but it shares your plan's limits, so what cloud session credits cover and when they run out decides whether it really keeps the job off your window.

Install Claude Code on an Ubuntu box and confirm it runs:

curl -fsSL https://claude.ai/install.sh | bash
claude --version

claude --version should print a version string such as 2.1.211 (Claude Code). A command not found here means ~/.local/bin is not on your PATH yet, so open a new shell and try again. That same installer is what you would run on a Linux desktop, where the CLI sits alongside the beta desktop app and the editor plugins.

Put the key in a file rather than in your shell history. Create ~/.claude-env in an editor with one line, export ANTHROPIC_API_KEY=sk-ant-your-key-here, then lock it down and load it:

chmod 600 ~/.claude-env
. ~/.claude-env
printenv ANTHROPIC_API_KEY | cut -c1-10

That last line prints the first ten characters, which is enough to confirm the variable is set without putting the whole key on screen.

Now start the job inside tmux so it survives your laptop closing:

tmux new -s overnight
claude --bare -p "Convert every test under ./tests from unittest to pytest, run the suite, and fix what fails" \
  --allowedTools "Read,Edit,Bash" \
  --append-system-prompt-file ./CLAUDE.md \
  --output-format json > ~/overnight.json

Detach with Ctrl-b then d, and close the connection. Reattach later with tmux attach -t overnight. Claude Code in a tmux session on a VPS covers the session handling in full.

--bare matters here. It skips auto-discovery of hooks, skills, plugins and CLAUDE.md, and it never reads OAuth credentials, so the run uses the API key and nothing else. That is what keeps the job off your subscription. It also means the project rules are gone, which is why --append-system-prompt-file hands them back deliberately. A -p run uses a set ANTHROPIC_API_KEY without asking either way, so the difference shows when the key fails to load: without --bare the run falls back to your subscription login, while with it the run fails on authentication and leaves your plan alone.

In the morning, read the result and the cost from the JSON:

jq -r '.result' ~/overnight.json
jq -r '.total_cost_usd' ~/overnight.json

Claude Code exits 0 on success and non-zero when the run fails, so a wrapper script can branch on the exit status and mail you the failure. Set a workspace spend limit in the Claude Console before you leave it running: an agent in a retry loop at 3am is a real way to spend real money. Cost control for agents you leave running goes through the caps worth setting first.

One bonus if you are on Max, Ultra or Team. Those plans now include monthly API credits for the Claude Platform: $100 a month on Max, $200 on Ultra, and on Team $20 per Standard seat and $100 per Premium seat, pooled and capped at $500. Interactive Claude Code is not covered, but a claude -p run you start yourself with an API key from your linked Console organization is, so this job can draw on them. Unused credits expire at the end of each billing cycle, and once they are spent the organization's API requests stop until next month's credits arrive unless it also holds purchased credits. If the job has to finish, keep some purchased Console credits behind it, or it stops with Credit balance is too low.

Give the job its own unprivileged user and its own git branch. An agent editing a repository unattended will occasionally do something you would have stopped, and a branch makes that a git checkout rather than an incident. Running a coding agent safely on a VPS covers the isolation.

For bulk work that is not interactive at all, such as classifying thousands of records, the Batch API processes requests asynchronously at a 50% discount on both input and output tokens. Most batches finish within an hour, but processing can take up to 24 hours.

What does not get your access back

Apart from upgrading, two things give your allowance back: the clock, and a limit reset if Anthropic has given you one. Limit resets are handed out occasionally to eligible plans, and using one puts either your five hour session limit or your weekly limit back to full right away, depending on the offer. You do not have to wait until you hit the limit to use it. Look for Reset for free in the Resets section of Settings and then Usage on the web or in Claude Desktop, or on the limit message itself. The button is not in Claude Code in the terminal, but the reset still applies there because the limits are shared.

Starting a new conversation does not restore your allowance. Usage is counted against your account, not against a conversation. It does make every following message cheaper, because a fresh conversation carries no history to re-read, so it is still worth doing. It is a cost cut, not a reset.

Deleting old conversations refunds nothing. Those tokens were spent when they were processed.

On Pro, Max and Ultra, switching models after a session or general weekly message does not restore the shared allowance. A message that names a model responds to /model, and Enterprise seat users can also try a lighter model after reaching a usage limit.

Retrying in a loop does nothing except keep your terminal busy. The reset time printed in the message is the real answer, and /usage will show you the same clock without the error. On a subscription, Claude Code 2.1.234 or later can wait in the open session and continue the interrupted task shortly after the reset, so you do not have to sit and watch it.

Upgrading is the one move that does raise the ceiling, so if the bars stay put after you pay, work through why a new plan can leave the old limits in place before you assume the allowance is broken.

FAQ

How long until my Claude limit resets?

The message tells you. Session limits run on a rolling five hour window and the message shows a clock time, such as resets 3:45pm. Weekly limits reset at a fixed time each week assigned to your account, and the message shows the day, such as resets Mon 12:00am. To see the bars and reset times that apply to your plan before you hit anything, run /usage in Claude Code, or open Settings and then Usage on claude.ai. Verified Ultra accounts have no five hour session limit. If Anthropic has given your account a limit reset, that same page shows a Reset for free button that puts the window back to full straight away.

Does switching to Sonnet get me working again?

Yes, when the message names a model, and Anthropic also recommends trying a lighter model for Enterprise seat users who reach a usage limit. After You've hit your Opus limit, run /model, choose a different model, and the session continues with your context intact. On Pro, Max and Ultra, after You've hit your session limit or You've hit your weekly limit, switching models does not restore the shared allowance. Switching to a cheaper model before you hit the wall is what actually stretches the window.

Will starting a new chat reset my usage limit?

No. Usage is counted against your account, so a new chat starts against the same empty allowance. It does make each following message cheaper, because a new conversation carries no history for Claude to re-read. /clear in Claude Code does the same thing and costs nothing, while /compact has to read the conversation it summarizes, so compacting a very large session is itself an expensive request.

Is the API cheaper than upgrading my plan?

It depends on how steady your usage is. The worked afternoon on this page costs $2.26 on Sonnet 5 and $1.13 on Haiku 4.5 at October 2026 list rates. A subscription is a flat fee for a capped allowance, so it wins when you work most days. Per token billing wins when your load is spiky, because quiet days cost you nothing at all.

Can I keep a job running while I wait for the reset?

Yes, if you move it off your subscription. Run it on a VPS with ANTHROPIC_API_KEY set in the environment and it bills per token instead of drawing on your plan window, so the two never compete. claude --bare -p inside tmux survives your laptop closing, and --output-format json writes a total_cost_usd field you can check in the morning with jq.