[FEATURE] When usage/plan limit is reached, offer a path to continue (switch account / add credits / upgrade) instead of only an error
Open 💬 0 comments Opened Jun 16, 2026 by alanafachini
Summary
When a usage / plan limit is reached, Claude Code only shows an error and a "wait for reset" message. It offers no path to keep working — no way to switch to another account, no way to add credits / top up, no upgrade call-to-action. The session just stops with an error.
What happens today
Mid-task, the plan's usage limit (e.g. weekly limit) is hit. The app shows a rate-limit / usage-limit error and a time to wait for renewal. That's it. The user is stuck until the reset window passes, with no actionable option presented inside the product.
Why this matters (usability / UX)
- It breaks a continuous workflow at the worst possible moment — mid-task — with no recourse but to wait, sometimes days.
- For paying users especially, there is genuine willingness to continue (top up, upgrade, or use another account they own) — but the product surfaces none of those paths.
- The only signal is an error. From a UX standpoint, hitting a limit is an expected state, not an error state, and it deserves actionable options, not a wall.
Proposed behavior
At the limit boundary, surface actionable ways to continue, for example:
- Switch account — let the user switch to another account they're already logged into.
- Add credits / top up — an inline option to purchase additional usage to continue immediately.
- Upgrade plan — a CTA to move to a higher tier.
- Clear reset info — show exactly when the limit resets, with a link to the relevant billing/usage page.
Even a single inline link to the right billing page at the moment of the limit would be a large improvement over today's dead-end error.
Related
- #26821 — rate limit still shown after weekly reset (a distinct bug). This request is specifically about offering continuation options at the moment the limit is reached.
Environment
- Claude Code — Desktop app
- macOS