Claude limit reach? Wetin you fit do next

Which Claude limit you hit

A Claude limit reached message dey name the window wey you dey wait for, and na that window dey decide wetin you fit do next. Session and weekly limits cover every model at once, so to switch model no go restore your access. Limit wey name one model na the exception: change model and you fit continue work while that model remain blocked.

Claude Code dey print the window and the time e go reset for 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 dey roll over every five hours. Weekly windows dey reset for one fixed time every week wey dem assign to your account, so the day and hour stay the same from one week to the next. Pro plan get the five-hour session window plus one weekly limit wey apply across all models. Max plan add another weekly limit wey apply only to one model family. The actual ceilings dey for the complete breakdown of Claude usage limits. This page dey start from where that one end.

Na this part dey confuse people. Every request count against the session window and the weekly window at the same time, so one heavy afternoon fit finish the weekly allowance while the five-hour window still get space. Check the reset time before you plan the rest of your day. Reset at 3:45pm na small break. Reset on Monday at midnight no be so.

Read meter before you guess

For claude.ai, open Settings, then Usage. Progress bars go show how much of the five hour session window and each weekly window you don use. So you fit see which one don empty instead of guessing.

For Claude Code, run /usage. E go show the same plan bars, plus breakdown of where recent usage go. E go attribute am to skills, subagents, plugins, and individual MCP (model context protocol) servers as percentage of the total. Press d for the last 24 hours and w for the last 7 days. E also go flag any pattern wey account for 10% or more of recent usage. The two patterns wey you go see most na long context and cache misses.

Two things to note. The breakdown dey calculate from session history wey dey stored for that machine. So work wey you do for another laptop or for claude.ai no dey inside, even though e use the same allowance, because Claude Code and your claude.ai chats share one subscription window. And the dollar figure for the Session block on top use standard list rates for API (application programming interface) users. This means say e no be your bill when you dey use subscription.

Smaller model change help?

Na e only work when message mention one model. After You've hit your Opus limit, run /model, choose Sonnet or Haiku, and session go continue with everything wey dey context. After You've hit your session limit or You've hit your weekly limit, /model no go change anything, because every model dey share those windows.

The switch dey far more useful before you hit the limit than after. Sonnet fit handle most coding work for a small part of Opus rate, so if you leave Opus as your default, na one of the two habits wey dey cause most unexpected usage. The other one na session wey you never clear. Give mechanical edits and log triage to Haiku, then keep Opus for the design decision wey genuinely hard for you. How to choose between Opus, Sonnet and Haiku explain where each one justify im price.

Stop dey pay for context wey you no dey use again

Claude Code dey send your complete conversation with every request. Every time Claude use tool, e dey send another request wey carry that batch of tool results. Prompt caching mean say system go read the history again for cached rate instead of full input rate. This make am cheaper, but e no make am free. So one-line question for session wey you don leave open since morning still dey use the whole conversation.

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

/clear no dey cost anything because e dey throw the context away instead of reading am. /compact must read the conversation wey e summarize, so compacting very large context na itself a large request. Use /clear when you move go unrelated work. Use /compact only when you dey inside task and you need make the thread continue. Run /rename before you clear am, so you fit find the session again with /resume.

Cache lifetime matter pass wetin plenty people expect. For subscription, cache dey live for one hour. E drop go five minutes once you dey use usage credits, and five minutes na also the default for API key. Your first message after long lunch no go find the cache. E go process the whole context again for full input price. Na why usage fit jump even when nothing visible change. Where prompt caching dey pay for itself explain the arithmetic.

Three more levers dey the same place. /mcp list the servers wey you configure, so you fit switch off the ones wey this task no need. Long CLAUDE.md dey load when session start, whether the work need am or not. So move specialized instructions go skills, wey go load only when you invoke dem. Extended thinking dey billed as output tokens, and na the expensive half. So reduce am with /effort, turn am off for /config, or set MAX_THINKING_TOKENS=8000 for model wey get fixed thinking budget.

Split the job so e fit enter one window

Press Shift+Tab to enter plan mode before any big change. Claude go inspect the codebase and suggest one approach for you to approve. If the direction no correct, catching am for there go cost one plan instead of two hours of edits plus rework.

Delegate noisy operations to subagents. If you run test suite or read 10,000-line log inside subagent, the raw output go remain for that subagent context. Na only the summary go return to your main conversation.

Press Escape immediately when Claude start going the wrong way. /rewind go restore both the conversation and the code to an earlier checkpoint, so you no go pay to undo work wey you never want.

Make you buy usage credits or use the API?

Usage credits fit make Pro or Max account continue work after plan allowance finish, and dem go bill am with standard API rates. Turn am on under Settings and then Usage for claude.ai after you attach payment method, or run /usage-credits for Claude Code. E go open your billing settings for browser. Credits apply to Claude conversations and Claude Code terminal usage. You fit set the monthly spending limit yourself with Adjust limit, or remove the limit with Set to unlimited. The command need subscription login, so e no dey available when you authenticate with API key. Free plan no offer credits at all. So the first step na Pro at $20 per month. See wetin Pro add and where e limits you explain how far that one fit carry you. If you dey add credits most weeks, bigger allowance usually cheaper. See the difference between the $100 and $200 Max tiers explain say the difference na usage multiplier, no be difference for models or features.

The other option na plain API key from Claude Console. Dem bill am per token, and e no get session or weekly window. One problem fit happen: stray ANTHROPIC_API_KEY for your environment fit override your subscription. For interactive session, Claude Code go ask once whether to use the key and remember your answer. So quick yes wey you give months ago fit easy escape your mind. Use custom API key toggle for /config fit change am back. For non-interactive -p run, e no go ask anything. E go use the key whenever the key dey set. You go notice am 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 na rate limit for the key, no be for your plan. Run /status and confirm say the active credential na the one wey you intend use. When login and API key both dey configured, /status mark the one wey no dey use.

One afternoon for API cost how much?

The worked example below na one afternoon of agent-style coding: 200,000 uncached input tokens, 1.8 million cache reads, and 150,000 output tokens. Prices na Anthropic list rates as of October 2026. Every rate dey quoted per million tokens, so if that unit still dey feel abstract, wetin one million tokens really worth go turn am to reading and writing amount wey you fit 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 cost $5.65 for Opus 5 and $1.13 for Haiku 4.5. Na output dey move the total: at $25 per million tokens for Opus 5 compared with $5 for Haiku 4.5, the 150,000 tokens wey Claude write cost pass the 2 million tokens wey e read. Na why reducing the thinking budget dey save more than trimming files. If the question na which provider to pay instead of which model to run, three jobs wey price for both Claude and ChatGPT APIs show where each bill cheaper.

One date pass without any change. Sonnet 5 launch at $2 and $10 per million input and output tokens, and dem announce am as introductory pricing through 31 August 2026, with plan to move to $3 and $15 for 1 September 2026. Anthropic cancel that increase and make $2 and $10 the standard price, so the same afternoon still cost $2.26 for Sonnet 5.

For scale, Anthropic own documentation put average Claude Code spending across enterprise deployments near $13 per developer per active day, and below $30 per active day for 90% of users, as of October 2026. Per-token billing no automatically cheaper than subscription. E dey win when your load dey come in spikes, because quiet days cost nothing, and e dey lose when you work every day. The API compared with subscription, using real numbers get the crossover point.

Run the long job for one VPS overnight

Some jobs no need you dey watch dem: big refactor, test migration, or documentation sweep. Those jobs no need your subscription window too. Put dem for one VPS (virtual private server) with an API key. Dem go use per token billing, while your plan allowance remain untouched for tomorrow interactive work.

Install Claude Code for one Ubuntu box and confirm say e dey run:

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

claude --version suppose print version string like 2.1.211 (Claude Code). If command not found show for here, e mean say ~/.local/bin never dey your PATH, so open new shell and try again. Na the same installer you go run for Linux desktop, where the CLI dey alongside the beta desktop app and editor plugins.

Put the key for file instead of your shell history. Create ~/.claude-env with editor and put one line, export ANTHROPIC_API_KEY=sk-ant-your-key-here, inside. Then lock the file down and load am:

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

That last line go print the first ten characters. That one enough to confirm say the variable dey set without showing the complete key for screen.

Now start the job inside tmux so e go survive when you close your laptop:

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 for tmux session on VPS explain the session handling complete.

--bare important for here. E skip auto-discovery of hooks, skills, plugins, and CLAUDE.md. E no ever read OAuth credentials too, so the run go use the API key and nothing else. Na this one keep the job away from your subscription. E also mean say the project rules don disappear, na why --append-system-prompt-file deliberately put dem back. A -p run dey use set ANTHROPIC_API_KEY without asking either way. The difference go show when the key no load: without --bare, the run go fall back to your subscription login. With am, the run go fail authentication and leave your plan untouched.

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

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

Claude Code dey exit 0 when e succeed, and non-zero when the run fail. So wrapper script fit check the exit status and send the failure to you by mail. Set workspace spend limit for Claude Console before you leave am running. Agent wey dey retry loop for 3am fit spend real money. Reduce CLAUDE_CODE_MAX_TOOL_USE_CONCURRENCY if you also want slow am down. Cost control for agents wey you leave running go explain the caps wey make sense to set first.

One thing to note if you dey use Max or Team. Those plans now include monthly API credits for linked Console organization. But Anthropic list Claude Code as not covered by those credits. So organization wey get only those credits go answer this job with Credit balance too low. Budget for purchased Console credits for this work.

Give the job its own unprivileged user and its own git branch. Agent wey dey edit repository without supervision fit sometimes do something wey you for stop. Branch go make am git checkout instead of incident. How to run coding agent safely for VPS cover the isolation.

For bulk work wey no interactive at all, like classifying thousands of records, Batch API dey process requests asynchronously with 50% discount for both input and output tokens. Na the cheapest per token option Anthropic publish, and overnight window match the latency wey e require.

Wetin no go restore your access

Apart from upgrading, na two things dey restore your allowance: time, and limit reset if Anthropic don give you one. Dem dey give eligible plans limit resets sometimes. If you use one, e go immediately restore either your five hour session limit or your weekly limit to full, depending on the offer. You no need wait until you reach the limit before you use am. Look for Reset for free inside the Resets section of Settings and then Usage on the web or for Claude Desktop, or look for am on the limit message itself. The button no dey inside Claude Code for the terminal, but the reset still apply there because all the limits dey shared. You no fit request one or trigger one by yourself. Na why every supposed way to reset a Claude usage limit dey fail once you examine am well.

Starting new conversation no restore your allowance. Your account dey carry the usage, not the conversation. But new conversation make every message after that cheaper because e no get old history to read again. So e still make sense to start one. Na cost reduction, no be reset.

Deleting old conversations no refund anything. The tokens don already spend when dem process am.

Changing model after session or weekly message no do anything because those windows dey shared across every model. Only message wey name a model respond to /model.

Retrying inside loop no do anything apart from keeping your terminal busy. The reset time wey the message show na the correct answer, and /usage go show you the same clock without the error. For subscription, Claude Code 2.1.234 or later fit wait inside the open session and continue the interrupted task shortly after the reset. So you no need sit down dey watch am.

Upgrading na the only action wey fit raise the ceiling. So if the bars remain the same after you pay, check why new plan fit leave the old limits in place before you conclude say the allowance don spoil.

FAQ

How long until my Claude limit resets?

The message dey tell you. Session limits dey run for rolling five hour window, and the message dey show clock time, like resets 3:45pm. Weekly limits dey reset for fixed time every week wey dem assign to your account, and the message dey show the day, like resets Mon 12:00am. To see both bars and both reset times before you reach any limit, run /usage for Claude Code, or open Settings and then Usage for claude.ai. If Anthropic don give your account limit reset, that same page go show Reset for free button wey go put the window back to full immediately.

Does switching to Sonnet get me working again?

Only when the message mention a model. After You've hit your Opus limit, run /model, choose another model, and the session go continue with your context intact. After You've hit your session limit or You've hit your weekly limit, model choice no go make difference, because those windows dey count every model together. If you switch to cheaper model before you reach the limit, na that one really dey stretch the window.

Will starting a new chat reset my usage limit?

No. Your usage dey count against your account, so new chat go start with the same remaining allowance. But e go make each message after that cheaper, because new conversation no get history for Claude to read again. /clear for Claude Code dey do the same thing and e cost nothing, while /compact still need read the conversation wey e dey summarize. So, compacting very large session na expensive request by itself.

Is the API cheaper than upgrading my plan?

E depend on how steady your usage dey. The afternoon example for this page cost $2.26 for Sonnet 5 and $1.13 for Haiku 4.5 with October 2026 list rates. Subscription na flat fee for capped allowance, so e better when you dey work most days. Per token billing better when your load dey come in spikes, because quiet days no go cost you anything.

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

Yes, if you move am away from your subscription. Run am for VPS with ANTHROPIC_API_KEY set for the environment, and billing go happen per token instead of drawing from your plan window. That way, both no go compete. claude --bare -p inside tmux go survive when you close your laptop, and --output-format json go write a total_cost_usd field wey you fit check in the morning with jq.