[BUG] /status Usage tab hangs on "Loading usage data…" in long-running sessions

Resolved 💬 3 comments Opened Apr 13, 2026 by dimension-zero Closed May 28, 2026

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?

The /status Usage tab displays "Loading usage data…" indefinitely in sessions that have been open for several hours (e.g. overnight). Other tabs (Status, Config) load fine.

Restarting the session fixes it immediately.

What Should Happen?

The Usage tab should

  • Best option: load the data (refresh connection/token if needed)
  • Second choice: show an error with a retry option
  • Last choice: display a message indicating the session needs to be refreshed

Error Messages/Logs

The "loading usage data..." message never resolves. No error is shown. No retry option is offered. Pressing r does nothing (the retry key-binding only activates on error state). The only fix is Esc, quit Claude Code and restart the session.

Steps to Reproduce

  1. Open a Claude Code session
  2. Leave it running for several hours (ideally overnight)
  3. Open /stats and navigate to the Usage tab
  4. Observe "Loading usage data…" shown indefinitely
  5. Quit Claude Code & restart - problem goes away

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

This issue has been around a long time.

Claude Code Version

2.1.104

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Guessed cause: the usage data fetch uses a connection or token that has expired overnight, but the UI only distinguishes between "error" and "has data" - and not "completed successfully with no data."

The loading indicator is shown whenever data is absent, regardless of whether a fetch is still unresolved. Hence suspicion that there's a silent fail that leaves the component permanently in the loading state.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗