[BUG] [session limit]

Resolved 💬 2 comments Opened May 26, 2026 by ronic009 Closed May 30, 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?

I am a subscriber to the paid premium tier ($100/month plan). Recently, I have noticed a significant and sensitive drop in the session limits. The "session limit reached" warning is triggering much faster than usual, even with standard usage and normal prompt lengths.

What Should Happen?

Expected Behavior:
The session limit should reflect the higher capacity promised for the premium tier, allowing for extended usage before triggering a limit.

Actual Behavior:
The session limit is reached rapidly, severely disrupting the workflow despite the premium subscription.

Error Messages/Logs

Steps to Reproduce

Log in with a paid premium account.

Start a new conversation or continue an existing one.

Observe that the usage limit warning appears much earlier than the expected capacity for this tier.

<img width="651" height="423" alt="Image" src="https://github.com/user-attachments/assets/74ff2cc3-ac88-4a15-b785-05e6a325abbc" />

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.147

Claude Code Version

2.1.150 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

<img width="643" height="459" alt="Image" src="https://github.com/user-attachments/assets/f0721c5a-c15a-4e94-ab31-848bcad8a22f" />

View original on GitHub ↗

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