[BUG] Claude Pro 5-hour session limit exhausted within 4 minutes of auto-resume after reset (v2.1.292)

Bug Description
Bug Description

I'm a paying Claude Pro subscriber experiencing a possible usage-accounting issue with Claude Code's automatic resume feature.

On October 8, 2026 (JST), my 5-hour session allowance was exhausted again approximately 4 minutes after it reset.

Steps to Reproduce / Timeline

At approximately 1:07 PM JST, Claude Code reached the session usage limit and displayed a reset time of 4:50 PM.

Claude Code automatically resumed at 4:50 PM.

The resumed session was interrupted, and I manually resubmitted my request.

At approximately 4:54 PM, Claude Code completed the task, including file generation and Git operations.

Immediately afterward, I submitted another request.

Claude Code immediately displayed:
You've hit your session limit · resets 9:50pm (Asia/Tokyo)

My newly reset session allowance was therefore unavailable after approximately 4 minutes.

Session Statistics

Subscription: Claude Pro

Model: claude-sonnet-5-5

API-equivalent cost: $38.78

Total API duration: 38m 53s

Total wall duration: 5h 3m 2s

Requests reported by prompt-cache statistics: 191

Cache read: 142.6 million tokens

Cache write: 1.9 million tokens

Output: 285.8k tokens

Context usage: 961.8k / 1m tokens (96%)

These statistics represent the cumulative session, not exclusively the four-minute window after the reset.

Expected Behavior

After the 5-hour session limit resets, I expect the renewed allowance to remain available unless actual usage legitimately consumes it.

Actual Behavior

The allowance appeared to be completely exhausted shortly after automatic resume, preventing me from starting any further work.

Request for Investigation

Could the maintainers investigate:

Whether automatic resume triggers excessive requests or unexpected token consumption when continuing a large-context session.

Whether prompt-cache reads or cache reconstruction are incorrectly accounted for after a session reset.

Whether usage-limit accounting correctly reflected the requests made between 4:50 PM and approximately 4:54 PM JST.

I understand that large-context sessions can consume substantial usage. However, exhausting the entire Pro allowance within minutes warrants verification.

Environment Info

Platform: win32

Terminal: windows-terminal

Claude Code version: 2.1.292

Subscription: Claude Pro

Feedback ID: 8aec54db-0e9d-4638-91e2-dc93b08259b0

Please let me know if additional sanitized diagnostic information would be helpful.
Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.292
• Feedback ID: 8aec54db-0e9d-4638-91e2-dc93b08259b0