Claude Code limit reached? What the message means and what to do next

When Claude Code says your limit is reached, you have used up either the five-hour session window or the weekly window on your plan, and the message tells you the reset time. You can wait, let Claude Code pick the task back up after the reset, pay for usage credits, or upgrade; UsageAtlas, a free desktop tracker, can warn you before the next one lands.

The message, decoded

Every developer timeline has the same screenshot by now: an agent halfway through a refactor, then a line in the terminal. According to Anthropic's error reference, it takes one of these forms:

• "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" or "You've hit your Sonnet limit"

A newer variant, "Usage limit reached · wrapping up", means you crossed the five-hour line mid-response and Claude Code is finishing the step it was on. Anthropic calls this a small, capped allowance that counts toward your weekly limit, and it is still rolling out.

The session and weekly limits cover every model, so /model does not get you out of them. The Opus and Sonnet messages are different: switching to a model from another family keeps you working.

Your five options

1. Wait for the reset. The time is in the message. /usage shows both windows and when each resets.

2. Let it continue on its own. Since v2.1.234, an interactive Claude Code session signed in with a subscription can wait and continue the task after the reset. The footer reads "Usage limit reached · limit resets" with the time, and Esc cancels. Keep the session open; if you exit, the wait ends.

3. Turn on usage credits. Run /usage-credits. On Pro and Max it opens Settings > Usage on claude.ai, where you can switch credits on and set a monthly spend limit. Past the limit, requests bill at standard API rates.

4. Upgrade. Anthropic suggests Max 5x for Pro users who keep running out, and Max 20x for Max 5x users.

5. Switch tools for an hour. Plenty of people move to Codex or Cursor while Claude Code resets. That works, but it is also how you lose track of what you spent where.

Why it happens sooner than expected

Requests count toward both windows at the same time. Anthropic's docs warn that a heavy burst, such as a big fan-out of subagents, can drain the weekly allowance before the session window even resets. Your Claude chat use and IDE use draw from the same pool too.

The /usage screen on paid plans lists what used your limits, by skill, subagent, plugin and MCP server, with suggested fixes. It is the first place to look when Tuesday already feels like Friday.

Getting a warning instead of a wall

Claude Code does show a heads-up, such as "You've used 85% of your session limit", but it only appears in the session. UsageAtlas puts the supported five-hour and weekly windows, remaining capacity and local reset times on your desktop, and sends one alert per reset cycle at a threshold you pick. It is free and open source, works without an account, and does not read prompts or responses. It tracks Codex, Cursor and Copilot in the same window, which covers option five.

If you only check once a day and never hit the wall, /usage on its own is enough.

Quick reference

FAQ

How do I know when my Claude Code limit resets? The limit message includes the reset time, and /usage lists both windows.

Does Claude chat use count toward my Claude Code limit? Yes. Anthropic says the limits are shared across Claude and Claude Code.