Claude Session Limit Reset Time: How the 5-Hour Window Works

The Claude Code session limit resets on a rolling 5-hour window starting from the first message you sent in that session. There is no fixed clock reset (like midnight UTC). Once 5 hours have elapsed from your first message, your session limit clears and you can start a new one. There is also a separate weekly usage cap that resets on a 7-day rolling basis. If you hit the weekly cap before a session expires, you must wait for the weekly window to roll over.

• Session window: 5 hours rolling from first message
• Weekly cap: resets on a 7-day rolling basis
• No fixed midnight or timezone reset

What is the Claude session limit?

Claude Code (the terminal-based agentic coding tool from Anthropic) enforces a usage cap per 5-hour period. When you exhaust your token budget within that window, you see a message like "You've hit your 5-hour message limit." The limit exists because Claude Code uses computationally expensive models (Sonnet, Opus) and the 5-hour window is how Anthropic rate-limits usage on Pro and Max plans. According to Anthropic's support documentation, usage is governed by both a short-term session cap and a longer-term weekly cap.

When does the session limit reset?

The reset is rolling, not fixed. The 5-hour clock starts ticking from the moment you send your first message in a session. If you started at 2:15 PM, your session limit resets at 7:15 PM. There is no universal reset time like midnight or 9 AM UTC shared across all users. Each user's window is personal and tied to their own usage start time. You can check how long is left by running /usage inside the Claude Code terminal, or visiting claude.ai/settings/usage.

See also: when does Claude Code usage reset and how long until Claude Code resets for more detail on the mechanics.

How does the session limit differ from the weekly limit?

Claude Code enforces two independent usage caps. Hitting either one will block you from continuing until that window resets.

Limit type	Window	Reset mechanism
Session limit	5 hours	Rolling from first message in session
Weekly cap	7 days	Rolling from first message in the week

The session limit is the one most developers hit day-to-day during heavy coding sprints. The weekly cap is a ceiling on total usage across the whole week. Both apply simultaneously. For a deeper comparison, see Claude Code weekly limit vs 5-hour lockout.

How do you check when your session resets?

There are three ways to see your current usage and when your session window ends:

• /usage command: Type /usage in the Claude Code terminal. It shows tokens used in the current 5-hour window and tokens remaining.
• claude.ai/settings/usage: The web dashboard shows your usage timeline and weekly consumption.
• Usagebar: A $9 one-time macOS menu bar app that shows your live 5-hour window progress, weekly cap status, and context usage at a glance. Sends notifications at 50%, 75%, and 90% so you know before you hit the wall.

The /usage command is the fastest in-terminal check. Usagebar is the best option if you want persistent ambient awareness without switching context. See how to check the Claude Code reset timer for step-by-step instructions.

Can you reset the session limit early?

No. As of September 2026, Anthropic does not provide a way to manually reset or purchase extra headroom within an active 5-hour window on Pro or Max plans. You must wait for the rolling window to expire. Some users try signing out and back in or starting a new project, but this does not reset the counter. The limit is server-side and tied to your account. For more on this, see can you reset Claude usage limit early.

Do Pro and Max plans have different session limits?

Both plans use the same 5-hour rolling session window structure, but Max plan users get a significantly higher token budget within each window. This means you can do more work before hitting the cap, not that the reset time changes. The rolling 5-hour mechanics are identical. According to Anthropic's documentation, Max plan usage limits are approximately 5x or 20x higher than Pro depending on the Max tier. See Claude Pro vs Max limits for a full breakdown.

What should you do when you hit the session limit?

When you see the session limit message, your options are:

• Wait it out: Check /usage for remaining time and resume when the 5-hour window resets.
• Switch to claude.ai: Claude.ai chat has a separate usage pool. It won't run agentic tasks but can answer questions while you wait.
• Use a different model tier: If you're on Pro, consider upgrading to Max for a larger session budget.
• Plan your sessions: Use Usagebar's 90% notification to finish or checkpoint your work before the hard stop hits.

For a full breakdown of what happens and your options, see you hit your 5-hour message limit on Claude and Claude Code message limit exceeded fix.

Key takeaways

1. The Claude Code session limit resets on a rolling 5-hour window from your first message, not at a fixed time.
2. A separate weekly cap resets on a rolling 7-day basis.
3. Use /usage in the terminal or claude.ai/settings/usage to see your current window status.
4. You cannot manually reset the session limit early.
5. Max plan users get more tokens per window but the same 5-hour reset mechanics.
6. Usagebar ($9 one-time) shows your reset timer live in the macOS menu bar with proactive notifications.

Sources

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