[BUG] 5-Hour Limit Not Renewed - Usage Shows New Session But Access Delayed by 2 Hours

Environment

• Platform:
• [x] Anthropic API
• Claude CLI version:

1.0.98 (Claude Code)

• Operating System:

Windows 11

• Terminal:

Git Bash, Command Prompt, PowerShell

Bug Description

My 5-hour Claude usage limit was expected to renew at the usual reset time, but instead, it was shifted 2 hours later. When I checked my usage, it clearly showed:

• A new session had started
• I had available tokens

However, Claude remained inaccessible during this time. This suggests a mismatch between what the usage system shows and how the limit is actually enforced.

Steps to Reproduce

1. I reached my 5-hour Claude usage limit.
2. I waited for the expected reset time, based on previous behavior.
3. At the reset time, I tried to use Claude via the CLI, but access was still denied.
4. I ran claude usage, which showed a new session with available tokens.
5. I fully logged out using claude logout, then logged in again with claude.
6. I retried the CLI command in Git Bash, Command Prompt, and PowerShell, but none of them worked.

Expected Behavior

Once the cooldown period ends and a new session appears with tokens available, Claude access should be restored immediately.

Actual Behavior

A new session with tokens appears, but Claude is still inaccessible for an extra 2 hours.

Additional Context

Screenshots are attached below showing:

• New session start time
• Available tokens
• Mismatch between session data and actual access time

<img width="850" height="457" alt="Image" src="https://github.com/user-attachments/assets/14a901dd-41e0-4f90-9aff-85cb7f50fcf6" />
<img width="853" height="474" alt="Image" src="https://github.com/user-attachments/assets/24acceff-4c22-4c10-b858-df8041c591c4" />