Warn users before hitting conversation rate limit
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
When a conversation hits the rate limit, the session terminates abruptly with no advance warning. This is functionally
disruptive — especially during long, multi-step editing workflows where context continuity matters.
The problem:
- No notification that the limit is approaching
- The session just stops, mid-task
- The user has no opportunity to save state, wrap up a logical checkpoint, or plan their next steps
- Resuming requires rebuilding context in a new session, which wastes time and tokens
Proposed Solution
What I'd expect:
- A warning when the conversation is approaching the limit (e.g., "You have approximately 10% of your usage remaining
for this period")
- Enough lead time to finish the current operation or checkpoint before the cutoff
- Ideally, a persistent indicator showing remaining capacity — similar to how API dashboards show token usage
Why it matters:
This is a paid account. Running out of capacity mid-workflow without warning is not a graceful experience. A simple
heads-up would make a significant difference in usability.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
I'm working on a code base and receive the notice that my session time has ended. It gives me no notice of how much change has occurred or what needs to be done in the future. If I had known I was at the end of my session, I would have saved the existing chagnes, and internally documented my next steps.
Additional Context
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗