[BUG] Pro Session Limit Drains to 100% Instantly After Reset (Catch-22: CLI Locked)

Resolved 💬 2 comments Opened Apr 27, 2026 by Kaito769 Closed Apr 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After my 5-hour Claude Pro limit resets, sending a single continuation prompt ("devam") results in the agent generating exactly one line of code and instantly triggering the "You've hit your limit" error again. This locks me out for another 5 hours.

<img width="1643" height="1010" alt="Image" src="https://github.com/user-attachments/assets/2b7ca1bc-96a2-4c3c-a77f-371cb57751a2" />

<img width="544" height="500" alt="Image" src="https://github.com/user-attachments/assets/1e5395ee-ce5e-46c5-aad5-c7732aec5af8" />

What Should Happen?

After a 5-hour reset, the session limit should be at 0% and allow normal usage. A single short prompt should not consume 100% of a Pro tier session quota.

Error Messages/Logs

You've hit your limit - resets [Time]
(This appears in the terminal immediately after 1 line of generation)

Steps to Reproduce

  1. Reach the 5-hour session limit on a Claude Pro account (using Claude AI OAuth, NOT an API key).
  2. Wait until the exact reset time passes.
  3. Send a single short prompt right after the reset.
  4. The system generates 1 line of code and instantly locks you out again, showing 100% session limit usage.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.120

Platform

Other

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

I am attaching screenshots that clearly show:

  1. The single line of code generated right after the reset, followed by the immediate limit error.
  2. My Account & Usage panel showing my Session is at 100% while my Weekly usage is only at 54% (confirming I am on a Pro plan, not an API key).

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗