What "Stop and Wait for Limit to Reset" Means in Claude Code (2026)

"Stop and wait for limit to reset" means Claude Code has hit either your rolling 5-hour usage cap or your weekly cap, and the CLI will refuse new prompts until that window rolls over. For most Pro and Max plan users, the 5-hour window resets on its own within a few hours; the weekly cap resets on a fixed day. Developers who hit this mid-task should use the wait time to review, test, or plan rather than retry repeatedly.

• Claude Code enforces a rolling 5-hour session limit plus a separate weekly limit on Pro and Max plans (Claude Support).
• You can check exact time-to-reset with the /usage command inside Claude Code, on claude.ai/settings/usage, or with a menu bar tool like Usagebar.
• Usagebar is a $9 one-time macOS menu bar app that tracks the 5-hour window, weekly cap, and context usage, with alerts at 50%, 75%, and 90% before you hit the wall.

What does "stop and wait" mean in claude code?

It means Claude Code has blocked further requests because you've used up your allotted capacity for the current billing window. Anthropic enforces this through two overlapping limits: a rolling 5-hour session cap and a weekly cap, both tied to your Pro or Max subscription tier (Claude Support, "Using Claude Code with your Pro or Max plan"). When either threshold is reached, the CLI returns a message telling you to stop and wait rather than letting requests queue or fail silently.

This is distinct from a hard outage. If Claude Code is also returning server errors or acting unresponsive, that's a service issue, not a usage cap, and waiting won't fix it.

How long do I have to wait for the limit to reset?

For the 5-hour session limit, the wait is never more than 5 hours from when your current window started, and often less if you're partway through. For the weekly cap, the wait can be up to a full week depending on when in the cycle you hit it. Anthropic documents both windows in its official plan guidance (Claude Support).

The exact countdown is account-specific and depends on when your current session window opened, so there's no universal number ("resets at 3pm" is wrong for most users). Check your own account to get the real figure, covered in the next section.

How can I check how much time is left until reset?

Run /usage inside the Claude Code CLI to see your current 5-hour and weekly consumption plus the exact reset timestamp, as documented in Anthropic's slash commands reference. You can also see the same data on the web at claude.ai/settings/usage.

Both methods require you to actively check and interpret percentages. For a passive always-visible option, a menu bar tool like Usagebar surfaces the same 5-hour window, weekly cap, and context usage without opening a terminal, and pushes a notification before you hit the wall instead of after.

What should I do while waiting for my claude code limit to reset?

Don't keep retrying the same prompt; it won't go through until the window resets and just wastes your attention. Use the downtime productively instead:

• Review and test the code Claude Code already generated this session
• Write out your next task or spec in plain English so you can paste it in immediately once reset
• Switch to a secondary tool (editor, docs, manual debugging) for lower-stakes work
• If you're on Pro and hitting this often, evaluate whether upgrading to Max fits your usage pattern

There is no supported way to force an early reset; the window is fixed by Anthropic server-side (see our breakdown on early resets).

How can I avoid seeing this message again?

Track your usage proactively instead of discovering the cap mid-task. The /usage command and claude.ai dashboard both work but require you to remember to check them. A background tracker closes that gap.

This is exactly what Usagebar does: a $9 one-time macOS menu bar app that watches your 5-hour rolling window, weekly cap, and context window usage simultaneously, firing alerts at 50%, 75%, and 90% so you can wrap up a task or switch tools before Claude Code stops you cold. No subscription, no account linking beyond local tracking.

Get Usagebar if you want to stop guessing when the next "stop and wait" message is coming.

5-hour window vs. weekly cap: what's the difference?

Limit type	Resets	Scope	Where to check
5-hour session cap	Rolls over 5 hours after window start	Prompt volume + model usage in that session	/usage, claude.ai/settings/usage, Usagebar
Weekly cap	Fixed weekly cycle	Cumulative usage across all sessions that week	/usage, claude.ai/settings/usage, Usagebar
Context window limit	Per-conversation, not time-based	Tokens in current chat/session	Usagebar (live), CLI warnings

Hitting the 5-hour cap is usually a short wait. Hitting the weekly cap on a busy project week is the one that actually hurts, which is why tracking both (not just one) matters. For more on how the weekly number is calculated, see when Claude Code usage resets.

Key takeaways

• "Stop and wait for limit to reset" is a usage cap message, not an outage, triggered by your 5-hour or weekly limit on Pro/Max plans.
• Check exact reset time with /usage, claude.ai/settings/usage, or Usagebar.
• The 5-hour window always resets within 5 hours; the weekly cap can take up to a week.
• There's no official way to force an early reset.
• Usagebar ($9 one-time) gives you a live, always-visible view of both limits plus context usage, with alerts before you get blocked.

Sources

• Claude Support: Using Claude Code with your Pro or Max plan
• Claude Code slash commands documentation
• Usagebar: Claude Code rate limit hit
• Usagebar: When does Claude Code usage reset
• Usagebar: Can you reset Claude usage limit early