[BUG]

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?

Title: Rate limits cut off sessions without warning - major UX flaw

Description:

I was cut off mid-session due to rate limits with zero warning. This is unacceptable for a
paid Pro subscription.

What should exist but doesn't:

1. Clear visibility of usage/limits - Users should see current usage and remaining capacity
2. Warnings before hitting limits - Alert at 80%, 90%, 95% so users can save work
3. Ability to save work state - Grace period or save functionality before cutoff
4. Better documentation - What are the actual limits? How are they calculated? When do they

reset?

Impact:

• Lost productive work mid-session
• Cannot plan work schedule around arbitrary limits
• Breaks trust in the tool for professional use
• Forces users to switch to competitors

Expected behavior:
Software should accommodate the user, not vice versa. Paid subscribers deserve transparency
and control over their usage.

Current workaround:
Canceling Pro subscription, moving to codex.

What Should Happen?

What should exist but doesn't:

1. Clear visibility of usage/limits - Users should see current usage and remaining capacity
2. Warnings before hitting limits - Alert at 80%, 90%, 95% so users can save work
3. Ability to save work state - Grace period or save functionality before cutoff
4. Better documentation - What are the actual limits? How are they calculated? When do they

reset?

Error Messages/Logs

Steps to Reproduce

Using claude code for an unknown amout of time/tokens.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

current

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_