You've hit your session limit · resets 5:30pm (Europe/Kyiv)

Resolved 💬 3 comments Opened Jul 6, 2026 by Miloslawsky Closed Jul 10, 2026

Bug Description
Title: [BUG] "You've hit your session limit" on fresh Max login while /usage and web dashboard both show session 0% Preflight Latest version (2.1.201) Single bug report Searched existing issues (looks related to #54177) What's wrong? Every prompt is rejected with You've hit your session limit · resets 5:30pm (Europe/Kyiv), but both usage panels report 0% on the current session: Claude Code /usage: Current session 0% used, resets 5:49pm (Europe/Kyiv); Current week (all models) 63%; Current week (Fable) 0%. claude.ai web dashboard (Settings → Usage): Current session 0% used, resets in 4h 43m; Weekly all models 63%; Fable 0%. The reset time in the error (5:30pm) does not match either panel (5:49pm / "4h 43m"), suggesting the enforced limit is decoupled from the displayed session meter. Steps to reproduce Log in with a Claude Max account (Login method: Claude Max account, no ANTHROPIC_API_KEY set). Confirm /usage shows 0% on the 5-hour session window. Submit any prompt (e.g. ping). Receive You've hit your session limit — every subsequent prompt is blocked. Things already tried (no effect) claude update → already on latest (2.1.201). claude logout / claude login → error persists immediately after successful login. mv ~/.claude ~/.claude.bak + fresh login → error reproduces on clean state. Switching model Fable 5 → Opus 4.8 via /model → no change. Verified ANTHROPIC_API_KEY is empty; login method is Claude Max account. Environment Claude Code 2.1.201 OS: Linux (Ubuntu) Plan: Max (20x) Model: Opus 4.8 Expected With session at 0%, prompts should be processed normally. Actual All prompts rejected with a session-limit error unrelated to displayed quota.

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.1.201
  • Feedback ID: 6b7fe8fe-b5ec-445d-927f-b28269caac78

Errors

[]

View original on GitHub ↗

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