[Bug] Session limit enforcement out of sync with actual usage after daily reset

Open 💬 1 comment Opened Jul 9, 2026 by mfahadaz1

Bug Description
My limits have already reset, but I'm still getting a session limit warning and can't proceed. This happened right after I tried to continue a session following the daily reset.
I'm attaching screenshots showing both the in-app usage panel and the Claude Code /status output, captured moments apart. Both agree that I'm well under my limits — session at ~3% used, weekly at 11% (all models) / 20% (Fable) — yet Claude Code is blocking all input with a session limit message. The enforcement and the displayed usage clearly disagree on the same account and machine.
Notably, the reset time the CLI quotes in the block message (11:50 PM) lines up with my session window reset rather than reflecting the ~97% of quota I actually have remaining, which suggests the internal limit tracking is out of sync with the server-side usage numbers.

<img width="1372" height="890" alt="Image" src="https://github.com/user-attachments/assets/a736c89e-92ae-4910-8169-402cca80a801" />

<img width="768" height="236" alt="Image" src="https://github.com/user-attachments/assets/04ebd0ad-8ed4-44c0-babc-3e78cfef1916" />

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.205
  • Feedback ID: 6b929558-d58f-4895-8cff-5f2fecb2bb20

Errors

[]

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗