You've Used 90% of Your Session Limit in Claude Code: What It Means and What to Do

The "you've used 90% of your session limit" warning in Claude Code means you're close to exhausting your token budget within the current 5-hour usage window. Once you hit 100%, Claude Code stops responding until the window resets. The warning fires at 90% so you have a small buffer to wrap up your current task before the lockout hits.

• Claude Code tracks usage in rolling 5-hour windows, not calendar days
• Pro plan users get a lighter allocation; Max plan users get 5x or 20x more headroom
• Usagebar shows your real-time session percentage in the macOS menu bar so you never get blindsided by this warning

What triggers the 90% session limit warning?

Claude Code measures your token consumption across a rolling 5-hour window. Every message you send, every file Claude reads, and every output Claude generates consumes tokens against that window's budget. When your cumulative token use crosses 90% of the window's cap, Claude Code surfaces the warning in the terminal. It's a soft nudge, not a hard stop — you can keep working, but you'll hit the wall soon.

The exact token cap per window varies by plan and is not published as a fixed number by Anthropic. It adjusts based on overall system load, which is why some sessions feel more generous than others. As of August 2026, Anthropic's support documentation confirms the 5-hour rolling window model for both Pro and Max subscribers.

How do Pro and Max plan limits compare?

Max plan subscribers get significantly more capacity per 5-hour window than Pro. Anthropic offers two Max tiers: one at 5x the Pro allocation and one at 20x. If you're hitting the 90% warning frequently on Pro, upgrading to Max 5x is often enough to eliminate the problem for typical solo development work.

Plan	Relative Session Capacity	Monthly Price
Claude Pro	1x (baseline)	$20/month
Claude Max (5x)	5x Pro	$100/month
Claude Max (20x)	20x Pro	$200/month

See the Claude Pro vs Max limits breakdown for a deeper comparison of what each tier gets you in practice.

When does the session limit reset?

The 5-hour window resets on a rolling basis from when you first sent a message in that window. If you started at 9:00 AM, your window clears at 2:00 PM. There is no fixed daily reset tied to midnight or a timezone. This is separate from the weekly aggregate cap that Max plan users also have. For full details on timing, see when does Claude Code usage reset.

The distinction between the 5-hour window and the weekly cap trips up a lot of users. You can be under your weekly cap and still get locked out of a session because the 5-hour window is exhausted. Both limits apply independently. The Claude Code weekly limit vs 5-hour lockout post covers exactly how these two counters interact.

What should you do when you see the 90% warning?

You have a few practical options depending on how urgent your work is.

• Finish the current task cleanly. Don't start large new operations. Wrap up what's in flight and commit your changes.
• Check your exact usage. Run /usage in Claude Code or visit claude.ai/settings/usage to see how close to 100% you actually are.
• Reduce token consumption. Use /compact to compress the conversation context. Avoid pasting large files wholesale — reference them by path instead. See how to reduce Claude Code token usage for a full list of techniques.
• Wait for the window to roll over. If you started a session 4 hours ago, you may only be minutes from a reset.
• Switch to a lighter model for remaining work. Claude Code can use Haiku or Sonnet for less demanding tasks, which consumes less of your budget.

How do you avoid hitting the 90% warning again?

The core problem is that Claude Code gives you no persistent visibility into your usage between sessions. You only find out you're close to the limit when Claude tells you — which is too late to plan around it.

Usagebar fixes this by sitting in your macOS menu bar and showing your current session percentage in real time. It tracks your 5-hour window usage, your weekly cap, and your context window consumption simultaneously. You can configure notifications at 50%, 75%, and 90% so you see the warning well before Claude Code does. It's a one-time $9 purchase with no subscription.

If you prefer the command line, /usage inside any Claude Code session gives you a snapshot. But you have to remember to check it. Usagebar makes the data ambient rather than something you have to pull manually.

For checking usage without tools, see how to check your Claude Code usage limits.

What happens when you hit 100% of the session limit?

Claude Code stops accepting new messages and returns a limit-exceeded error. Any in-progress task is halted. You cannot override or extend the cap — you wait for the 5-hour window to roll over or for the weekly cap to reset (on Monday, UTC). If you hit this wall regularly, it's a sign your usage pattern doesn't fit the Pro plan. See Claude Code message limit exceeded fix for recovery steps.

Key takeaways

1. The 90% warning fires when you've consumed 90% of your token budget in the current rolling 5-hour window.
2. The 5-hour window and weekly cap are separate counters — both can independently cut off your session.
3. Run /usage or check claude.ai/settings/usage to see your exact percentage.
4. Use /compact and model switching to stretch remaining budget.
5. Usagebar ($9 one-time) gives you ambient, real-time session tracking in the macOS menu bar with configurable alerts at 50%, 75%, and 90%.

Sources

• Anthropic Support: Using Claude Code with your Pro or Max plan
• claude.ai/settings/usage