What should I do when I hit my Claude limit?
Short answer
First read the message: it names the limit and its reset time. For a session or weekly limit, wait for the reset (Claude Code v2.1.234 and later can continue on its own), turn on usage credits to keep working at API rates, or upgrade. For an Opus or Sonnet limit, switch to a model outside that family with /model.
On this page
Which limit did you hit?
| Message | What it means | What keeps you working |
|---|---|---|
You've hit your session limit · resets 3:45pm | The 5-hour window, shared by all models | Wait, usage credits or upgrade |
You've hit your weekly limit · resets Mon 12:00am | The weekly limit, all models | Usage credits, upgrade or wait |
You've hit your Opus limit or Sonnet limit | That model family only | /model to another family |
Usage credits required for 1M context | An entitlement check, not a used-up quota | /model to standard context, or turn on usage credits |
Opus is experiencing high load | Capacity on one model; does not count against your quota | /model to another model |
The session and weekly limits are shared across all models, so switching models does not restore access. The Opus and Sonnet limits apply only to that family.1 Run /usage to see both bars and their reset times, or /rate-limit-options for the ways to keep working: wait, add usage credits or upgrade.2
1. Wait, and let Claude Code continue
From v2.1.234, an interactive Claude Code session signed in with a claude.ai subscription waits through a usage limit and continues the task after the reset. It is on by default. Keep the session open; Claude Code picks the task up where it stopped instead of resending your message.3 It does not start this wait on its own when the reset is more than 24 hours away, as a weekly reset can be, and it stops after three automatic continuations in a row; /rate-limit-options then lets you choose a wait yourself.3 More in when the 5-hour limit resets.
2. Switch model family for a model-specific limit
After an Opus or Sonnet limit, run /model and pick a model outside that family. Each model has its own prompt cache, so the first request after the switch re-reads the whole conversation with no cache hits.1 If you switch with /model during an automatic wait, Claude Code checks whether usage is available and continues right away if it is.3
3. Turn on usage credits
Usage credits let Pro, Max and Ultra subscribers keep going past a limit. With them on, "Your requests switch to pay-as-you-go pricing on usage credits and keep working", billed at standard API rates, until you reach your monthly spend limit or your balance runs out with auto-reload off.4 In Claude Code, /usage-credits opens Settings > Usage on claude.ai; on Team and Enterprise it opens organization settings or sends a request to your admins.5 Costs, caps and expiry are in how usage credits work.
4. Move to a higher plan
Anthropic says that if you upgrade, your new plan's limits apply right away.6 The steps are Pro at $20 a month, Max at $100 with 5x Pro usage per 5 hours and per week, and Ultra at $200 with no 5-hour limit for verified accounts.7 If you upgrade with /upgrade and sign back in during a wait, Claude Code checks for available usage and continues; it does not check after an upgrade you make on your own in a browser.3 See which plan to get for Claude Code.
5. Use another subscription you already pay for
If you already pay for a second Claude subscription for your own work, for example one for client work and one for your own projects, each has its own limits. Anthropic documents CLAUDE_CONFIG_DIR for running several accounts side by side, for example CLAUDE_CONFIG_DIR=~/.claude-work claude.8 Session history is stored under each folder,8 so an agent started under the other account begins a new conversation; give it a short handoff note. Setup is in running more than one Claude account.
Make the next window last longer
- Open
/usageand read the recommendations. Each row starts with the share of recent usage it applies to, andfapplies the ones Claude Code can.5 - Use
/clearbetween unrelated tasks. A session open all day sends its whole history with every request.5 - Use Sonnet for most coding and keep Opus for hard problems. Subagents' own requests count too, and can run on a smaller model.5
- Stop
/loopruns and scheduled tasks you no longer need. They fire while the session is idle.5
Common questions
Will switching models get me past a session limit?
No. The session and weekly limits are shared across all models. Switching with /model only helps after an Opus or Sonnet limit.
Do usage credits start charging on their own?
Only if you turned them on in Settings > Usage. Then requests past a limit switch to pay-as-you-go pricing at standard API rates until you reach your monthly spend limit or your balance runs out with auto-reload off.
Can I open another account to get more usage?
Anthropic's Usage Policy prohibits creating multiple accounts to circumvent product guardrails, and its Consumer Terms forbid sharing an account. Usage credits and higher plans are the supported ways to get more usage. This is not legal advice.
Is a high-load message the same as hitting my limit?
No. Claude Code's docs say a 529 high-load error is not your usage limit and does not count against your quota. Switching to another model with /model usually keeps you working.
Sources
- Error reference: You've hit your session limitClaude Code docsUndated. Checked
- CommandsClaude Code docsUndated. Checked
- Interactive mode: Wait for a usage limit to resetClaude Code docsUndated. Checked
- Manage usage credits for paid Claude plansAnthropic Help CenterPage shows "Updated this week". Checked
- Manage costs effectivelyClaude Code docsUndated. Checked
- How do usage and length limits work?Anthropic Help CenterPage shows "Updated over a week ago". Checked
- Plans and pricingAnthropicUndated. Checked
- Environment variables: CLAUDE_CONFIG_DIRClaude Code docsUndated. Checked
- Consumer Terms of ServiceAnthropicEffective
- Usage PolicyAnthropicEffective