Session usage limit hit unexpectedly fast after a reset, with no manual token-heavy input on my part.

Bug Description
Platform: Windows, Claude Code (terminal) Issue: Session usage limit hit unexpectedly fast after a reset, with no manual token-heavy input on my part. What happened: 1. Was working in an active Claude Code session on a project (FMEA/YAML data work) when a 502 server error interrupted a response mid-task. 2. Typed "continue" to resume — session picked back up and kept working. 3. Hit the 5-hour session limit (message: "You've hit your session limit - resets 7:40pm (Asia/Kolkata)"). 4. Waited for the reset, then typed "continue" again to resume the same session — no other sessions were running. 5. The session ran an extended autonomous task (~44 minutes, including recursive grep/search across multiple YAML files) and hit the session limit again shortly after, this time with a much later reset ("resets 12:50am (Asia/Kolkata)"). What's confusing: from my side, I only typed "continue" a couple of times — I didn't send long prompts or large files myself. It wasn't clear that the autonomous tool calls (file reads, grep, bash commands) during a long-running "continue" session count so heavily against the 5-hour limit, or that resuming right after a reset could burn through a fresh window that fast. Request: Could you clarify (a) whether a mid-response 502 error itself consumes usage even though no output was delivered, and (b) whether there's a way to see live usage consumption during an autonomous/long-running task, so I can stop it before hitting the limit instead of finding out after the fact? A visible running counter during long tool-heavy sessions would help a lot and i prefer for refund of my wasted session tokens by this bug.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.267
• Feedback ID: fcf36fa9-1e31-4829-a13b-1ab823f5819f

Errors

[]