XCR

Guides

Claude Code usage limit reached? Here's how to keep coding

Updated

Short answer

Claude Code on the Pro and Max plans has two limits: a session limit that resets every five hours, and a weekly limit. When you hit one, you can wait for the reset, turn on usage credits, upgrade your plan or switch to API billing. To make each session go further, hand the heavy implementation work to a plugin like XCR, so Claude Code spends its turns on planning and review.

What "usage limit reached" means

As of October 2026, Anthropic's Pro and Max plans give Claude Code two allowances:

  • A five-hour session limit. Your session allowance refreshes every five hours.
  • A weekly limit. It resets at a fixed time each week assigned to your account.

Both are shared with claude.ai and Claude Desktop, so a long chat in the browser draws from the same pool as your coding session. Claude Code warns you as you get close. If you hit the session limit mid-response, you may see "Usage limit reached · wrapping up" while it finishes the step in progress.

Why Claude Code runs out so fast

Usage depends on how much the model has to read and write, not on how many messages you send. The usual culprits:

  • Large context. Every turn re-reads the conversation so far, plus every file Claude Code has opened.
  • Agent loops. Writing code, running tests, reading the failure and trying again can take dozens of turns for one feature.
  • Big repositories. Exploring an unfamiliar codebase means reading many files before writing a single line.
  • The most capable models and higher effort settings. They use your allowance faster than lighter ones.

A multi-file feature with a few rounds of test fixes can easily use more of your session than an afternoon of small edits.

Usage limit vs. rate limit

They are different things. A usage limit is your plan's allowance over five hours or a week. A rate limit (often an HTTP 429 or "rate limit exceeded" error) applies when you run Claude Code with an API key: you pay per token, and your account tier caps how many requests and tokens you can send per minute. A rate limit clears in seconds or minutes. A usage limit clears at your reset time.

How to check what you have left

Type /usage in Claude Code, or open Settings > Usage on claude.ai. You'll see progress bars for the current session and the weekly limit, plus the reset times.

Your options when you hit the limit

  1. Wait for the reset. Free, but it stops your work for hours, or days if it's the weekly limit.
  2. Turn on usage credits. Pay for extra usage and keep going on your current plan.
  3. Upgrade. Max 5x and Max 20x offer five and twenty times Pro's per-session allowance.
  4. Switch to API billing. A Claude Console account bills per token, with no plan limit.
  5. Move the heavy work elsewhere. Keep Claude Code for planning, questions and review, and send the big implementation jobs to a tool built for them. More on that below.

Make every session go further

  • Run /clear when you switch to an unrelated task, so old context stops riding along.
  • Use /compact in long sessions to shrink the history.
  • Keep CLAUDE.md short and specific. It's loaded into every session.
  • Name the files that matter instead of asking Claude Code to search the whole repo.
  • Describe the whole change in one message instead of drip-feeding requirements.
  • Use /model to pick a lighter model for routine edits.

We collected more in 8 ways to make AI coding cheaper.

Hand the heavy lifting to XCR

XCR is a free plugin that works like an AI switchboard for your AI coding tool. It plugs into Claude Code, Codex, Cursor and Grok Build, and takes over the expensive part of the job:

  1. Your tool hands the task over. When a request needs more than a small edit (roughly more than 30 lines, or more than one file), it goes to XCR first.
  2. XCR does the build. It reads the repository itself, writes the change on a copy of your project, runs your project's own checks (type check, lint, tests) and repairs failures within the task budget.
  3. You get a short report. Requirements done, files changed, check results and the exact cost.
  4. Your tool reviews and wraps up. It checks the change against your request and finishes anything that needs the internet, such as installing packages.

XCR routes each task to models from OpenAI, Anthropic and Google, so one account covers all of them. Small edits and quick questions stay in your tool, exactly as before.

Pricing: model cost plus 20%, plus $0.02 per task. Credit packs of $5, $10, $25 or $50. No subscription. In our 22-task self-test sample, XCR and GPT-6 Astra each completed 19 tasks, and XCR's estimated cost was 41.8% lower.

In Claude Code, XCR registers as an MCP server and adds one short rule to your CLAUDE.md, so the hand-off happens on its own. See how the plugin works.

Keep Claude Code. Hand the heavy work to XCR.

Free plugin, installed in about a minute. Pay per task, with no subscription.

Install XCR free →

Questions

How long does it take for the Claude Code limit to reset?+

The session limit resets every five hours. The weekly limit resets at a fixed time each week assigned to your account. Run /usage in Claude Code to see your exact reset times.

Does XCR use my Claude subscription?+

No. XCR runs its tasks on its own model access and bills them to your XCR credit. Claude Code still handles your conversation, the hand-off and the final review.

Which tasks does Claude Code hand to XCR?+

Changes beyond a small edit: roughly more than 30 lines or more than one file, such as features, tests, bug fixes, refactors and migrations. Quick questions and one-line fixes stay in Claude Code.

Is XCR made by Anthropic?+

No. XCR is an independent plugin. Claude Code is named only to describe compatibility.

More guides

All guides