[BUG] Five-hour session quota immediately shows 100% at reset across VS Code and mobile
Summary
Claude Pro five-hour session quota immediately showed 100% used at the expected reset boundary, blocking Claude Code in VS Code and the same account on mobile.
Environment
- macOS; Claude Code VS Code extension
- Pro subscription
- Model shown: Opus 5.5, Medium
- October 10, 2026; Asia/Taipei (UTC+8)
- Exact extension/CLI version not yet collected
Observed sequence
- Before reset, the usage meter showed 98% used with two minutes remaining.
- At the expected reset boundary it immediately showed 100% used. No usable new allowance was observed.
- A Claude Code task was active around the boundary. This report does NOT claim zero activity or that background consumption has been ruled out.
- Mobile showed the same five-hour limit state.
- VS Code showed
You've hit your session limit · resets 12pm (Asia/Taipei)at 07:03 and 07:04 local time. - Web Settings > Usage was independently checked afterward: current session 100%, next reset 12:00; weekly usage 70%; no limit reset available. The visible weekly quota was not exhausted.
Expected behavior
The session meter should accurately reflect a successful reset and actual subsequent usage. A newly reset allowance should not immediately be exhausted unless verified consumption supports that result.
Investigation requested
Please investigate reset accounting and attribution of in-flight requests, including potential duplicate or stale usage accounting. If erroneous consumption is confirmed, please correct the quota. Account-specific details can be coordinated privately with support; no account identifiers, project files or conversation transcripts are included here.
Private support was contacted, but the bot stated it could not inspect account usage/reset logs or transfer the conversation to a human.
Related report
https://github.com/anthropics/claude-code/issues/40513 describes a similar visible symptom. This report's root cause is not yet known.