[BUG] /usage view traps all input, no way to dismiss
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?
Description
The /usage command traps all keyboard input with no way to dismiss the view. The only way out is Ctrl+C /
Ctrl+D, which kills the entire Claude process.
Steps to reproduce
- Open Claude Code CLI
- Type /usage
- Try to exit the view
What happens
- Escape does not dismiss the view
- Tab works to switch between tabs within the view
- No other keybinding dismisses it (tried :q, q, Escape)
- The usage tab shows a rate limit error (rate_limit_error: Rate limited. Please try again later.) despite
the conversation API working fine in the same session
- The only way out is Ctrl+C or Ctrl+D, which terminates the process entirely
What was tried
- Toggling vim mode off — no difference
- Running in both Fish and Bash shells — same behavior
- Escape, Tab, :q, q — none dismiss the view
- Only Ctrl+C/Ctrl+D work, but they kill the process
Environment
- Version: 2.1.86
- Shell: Fish and Bash (both affected)
- OS: Linux (NixOS)
What Should Happen?
Escape (or some keybinding) should dismiss the /usage view and return to the chat prompt without killing the process. The rate limit error on the usage endpoint while actively in a session is also unexpected (I am well below the limit).
Error Messages/Logs
Error: Failed to load usage data: {"error":{"type":"rate_limit_error","message":"Rate limited. Please try again later."
Steps to Reproduce
Type /usage at any point. Get stuck forever.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.86
Platform
Anthropic API
Operating System
Other Linux
Terminal/Shell
Other
Additional Information
Issue terminal independent (tried on xterm, issue never appeared on other terminals, only after update).
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗