[BUG] usage limit / session management bug in Claude Code.

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

I encountered an issue with Claude Code session limits.

My session reached 100% usage and the interface showed that the session
would reset at 11:00 AM. However, when the reset occurred, the session
did not unlock. Instead, it immediately remained locked in cooldown.

This appears inconsistent with the usage dashboard:

• Current session: 100% used
• Weekly limits: only ~14% used
• Sonnet usage: ~2% used

Because the weekly limit is far from exhausted, it seems the session
reset did not correctly clear the session usage state.

Expected behavior:
After the session reset time passes, a new session should start and
Claude Code should become usable again.

Actual behavior:
The session remains locked in cooldown immediately after reset.

This may indicate a session reset state bug.

Plan: Max
Models used: Opus and Sonnet
Approximate time of reset: 11:00 AM
Weekly usage remaining: ~86%

<img width="942" height="369" alt="Image" src="https://github.com/user-attachments/assets/a5e96f68-ae85-4888-9b67-65d4e35a6de3" />

What Should Happen?

After the session reset time (11:00 AM), the session usage should reset and Claude Code should allow starting a new session.

The system should not immediately place the account into cooldown if the weekly limit has not been reached. In my case, the weekly limit shows only ~14% used, so a new session should have been available.

Additionally, it seems unrealistic that 14% of the weekly usage limit could be consumed in under two hours of normal usage. This suggests the session limit and weekly limit calculations may not be aligned correctly, or the reset logic may not be properly clearing session state after the scheduled reset time.

Expected behavior:
When the session reset occurs, the session usage should return to 0% and Claude Code should allow continued usage.

Error Messages/Logs

You've hit your limit · resets 4pm

Steps to Reproduce

1. Start a Claude Code session using Opus and Sonnet models.
2. Use Claude Code continuously for an extended development session until the session usage reaches 100%.
3. Wait for the session reset time shown in the UI (11:00 AM).
4. After the reset time passes, attempt to start a new Claude Code session.

Result:
The session remains locked in cooldown even though the reset time has passed.

Additional context:
The usage dashboard shows only ~14% of the weekly limit used (~86% remaining), so the session should have been available again after reset.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.70 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_