You've hit your session limit · resets 4:20pm (Asia/Calcutta)

Bug Description
I'm on the Pro plan. Today (Aug 20, IST) a Claude Code session in /Users/ashwath/projects/drawmaid hit "You've hit your session limit · resets 4:20pm (Asia/Calcutta)" mid-window at 12:02 IST — blocked on a WebSearch tool call, moments after a Bash call succeeded ("CLAIMED").

The 5-hour window in question (≈11:20→16:20 IST) contained only ~13 user messages and ~4.7M total tokens: 2.96M cache-write, 1.78M cache-read, and just ~10.7K output + ~4.7K thinking. No usage from earlier windows (a 105-message midnight run) overlaps this window.

Every turn in this session carried a ~590K-token context (cache-write/read), which I understand counts messages on a heavily context-weighted basis on Pro. If a ~590K-context turn costs many message units, 13 turns hitting the cap is technically possible — but it's invisible to me, and my transcript shows an order of magnitude less usage than a normal window.

Attached: raw session transcript (d4d6a8ed-*.jsonl). Could you confirm (a) the message-unit cost of a ~590K-context turn on Pro, and (b) the exact running total for that window? I want to know if ~4.7M tokens worth of mostly-cache traffic is really meant to exhaust a Pro window.

Environment Info

• Platform: darwin
• Terminal: ghostty
• Version: 2.1.237
• Feedback ID: ee5dbaf1-d3c5-4431-b6ec-d9a453330433

Errors

[]