[BUG] /usage panel shows stale data until first prompt is sent
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?
Environment
- Claude Code CLI
- Platform: Windows 10 Pro (10.0.19045), Git Bash
- Model: Opus 4.7
Steps to reproduce
- Start a fresh session (claude in terminal).
- Immediately type /usage without sending any prompt first.
- Observe the usage panel values (session limits, weekly limits, remaining quota).
- Dismiss the panel, send any prompt (e.g. test), wait for a reply.
- Open /usage again.
Expected
Step 3 shows the current usage figures, matching what step 5 shows.
Actual
Step 3 shows stale/pre-session values. Only after a real prompt round-trip (step 4) does /usage reflect the current state. This makes the pre-prompt check useless — the user cannot
inspect remaining quota before deciding whether to spend it.
Impact
Users who open /usage specifically to decide whether to start work on a limited quota get outdated numbers, defeating the purpose of the panel.
Suggested fix
Fetch usage on panel open, not only piggy-backed on prompt responses. Alternatively trigger a lightweight refresh call when the /usage slash command is invoked.
What Should Happen?
"/usage" should shows actual data
Error Messages/Logs
Steps to Reproduce
- Open Claude
- Print and send /usage
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.278
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_