[BUG] Claude does not continue after "Claude usage limit reached. Your limit will reset at 2pm (America/New_York)"

Environment

• Platform (select one):
• [ x] Anthropic API
• [ ] AWS Bedrock
• [ ] Google Vertex AI
• [ ] Other: <!-- specify -->
• Claude CLI version: <!-- output of claude --version --> 1.0.83
• Operating System: <!-- e.g. --> Ubuntu 25.04
• Terminal: <!-- e.g. iTerm2, Terminal App --> bash

Bug Description

Whenever Claude Pro stops because of a usage limit, when the time limit resets, I ask it to continue, and it has lost context of what it was doing when the interruption occurred. This is a fundamental flaw. It wastes tokens in the next session trying to figure out what to do next, often going back and redoing work that was already finalized.

Steps to Reproduce

1. <!-- First step --> Start a long duration task
2. <!-- Second step --> Use up all tokens until limit expires
3. <!-- And so on... --> After the mandated delay, ask Claude to resume where it was before the usage limit was reached

Expected Behavior

<!-- What you expected to happen --> Claude should continue exactly where it was interrupted without wasting tokens on figuring out what to do next, often missing the context and wasting even more tokens

Actual Behavior

<!-- What actually happened --> Claude never resumes the interrupted step. It always goes back to reading the plan and gets it wrong most of the time.

Additional Context

<!-- Add any other context about the problem here, such as screenshots, logs, etc. -->