[BUG] Persistent 5-hour reset loop / 100% usage exhaustion with zero activity

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?

Bug Description

My Pro account is stuck in a "phantom" usage loop. Every time the 5-hour cooldown timer reaches zero, the system systematically pushes the lockout back another 5 hours (e.g., 08:30 AM -> 01:30 PM -> 06:30 PM) without allowing any messages to be sent. I have had zero usage for the last 3 days and significantly reduced usage for the past week due to this persistent reset bug.

This is affecting me across all platforms: Web, Desktop, and Claude Code CLI.

Related Issues

This appears heavily related to #69995, #68864, #69160, and #64491 (which specifically details automatic consumption with zero activity).

Steps to Reproduce

1. Wait for the indicated reset time (e.g., 01:30 PM).
2. Open Claude (Web or CLI).
3. Observe that the session is instantly at 100% usage and a new 5-hour countdown has started automatically without sending any prompts.

Expected Behavior

The 5-hour session timer should reset to 0% usage, allowing fresh prompts to be sent.

Actual Behavior

The session immediately locks out at 100% usage and pushes the reset target back by another 5 hours.

Environment Info

• Platform: Windows 11
• Terminal: PowerShell / Command Prompt
• Version: 2.1.197
• Account Type: Pro

Additional Context

I have already tried logging out of all devices, clearing cache/cookies, and using incognito mode with no success. The issue persists across different networks and devices, indicating a server-side desynchronization loop.

What Should Happen?

The 5-hour session usage counter should completely reset to 0% after the cooldown period ends, allowing me to send new messages and use the platform normally.

Error Messages/Logs

- "You've hit your session limit · resets 01:30 PM"
- Upon reaching 01:30 PM, the system immediately changes to: "Resets in 4 hr 29 min" without allowing any usage.
- Session status page stays stuck at 100% used.

Steps to Reproduce

1. Wait for the active 5-hour limitation cooldown window to hit its target end time (e.g., 01:30 PM).
2. Open Claude via Web browser or run a command in the Claude Code CLI.
3. Observe that access is still completely blocked, the usage counter remains stuck at 100%, and a brand new 5-hour countdown has been automatically forced onto the account.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.197

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This issue completely breaks usability. The server-side rate-limiting logic is trapped in a rolling loop that automatically compounds.

I have already escalated this via email to the support team along with diagnostic screenshots of the 100% locked usage dashboard.