[BUG] 5-hour session limit shows "limit reached" while usage panel displays non-zero remaining capacity

Open 💬 0 comments Opened Jul 15, 2026 by BOT-K4CP3R

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?

Claude Code blocks further usage with a "5-hour limit reached" error, while the usage panel simultaneously shows non-zero remaining capacity (1-2%) for the 5-hour session limit. This only happens in Claude Code — the web app / claude.ai interface does NOT show me as rate-limited on the same account at the same time.

What Should Happen?

A hard "limit reached" block should only trigger when remaining capacity is 0%. Session limit state should be consistent between Claude Code and the web app for the same account.

Error Messages/Logs

"5-hour limit reached. Try again after your limit resets." — shown despite usage panel displaying 1-2% remaining capacity.

Steps to Reproduce

  1. Wait for 5-hour session limit to reset
  2. Send a small number of short messages in Claude Code (minimal usage)
  3. Usage panel shows ~1-2% remaining capacity for the 5-hour limit
  4. Claude Code blocks with "5-hour limit reached" despite non-zero remaining %
  5. Simultaneously check claude.ai web app on the same account — no rate limit shown

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

2.1.185

Claude Code Version

2.1.185

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Weekly limits at the time of the issue: all models 21% used, Fable 27% used — confirms this isn't overall heavy usage, points specifically to a Claude Code session-tracking/enforcement bug. Already raised via support chat (Fin AI Agent, conversation ID: 215475087838192), confirmed as unusual by the agent, escalated but human support cannot manually reset limits — filing here as this is a bug report, not a reset request.

View original on GitHub ↗