[BUG] /usage in v2.1.139 — 5-hour and weekly progress bars no longer rendering (regression from v2.1.138)

Resolved 💬 3 comments Opened May 11, 2026 by Ceasar29 Closed May 15, 2026

Summary

After updating to v2.1.139, the 5-hour session bar, weekly bar, and weekly Sonnet-only bar no longer render in /usage. Reset times and percentages are gone too. Only the "What's contributing to your limits usage?" attribution view remains. Confirmed working in v2.1.138 earlier the same day on the same account/machine.

This makes it impossible to see how much of the rate-limit windows have been consumed without leaving the CLI and logging into claude.ai per account — a serious workflow regression for anyone running multiple parallel sessions.

Environment

  • Claude Code: 2.1.139
  • OS: WSL2 (Ubuntu) on Windows 11
  • Shell: bash
  • Plan: Max subscription
  • Reproduced across multiple accounts on the same machine

Steps to reproduce

  1. Update to v2.1.139.
  2. Run /usage.
  3. Navigate to the Usage tab.

Expected (v2.1.138, working)

Current session
████▌                                              9% used
Resets 3:30pm (America/Los_Angeles)

Current week (all models)
███████████████████▌                               39% used
Resets May 17, 10am (America/Los_Angeles)

Current week (Sonnet only)
██████████████████████                             44% used
Resets May 17, 10am (America/Los_Angeles)

Actual (v2.1.139, broken)

Session

Total cost:            $0.0000
Total duration (API):  0s
Total duration (wall): 3s
...

What's contributing to your limits usage?
...

The "Current session" / "Current week (all models)" / "Current week (Sonnet only)" bar blocks and their reset times are gone entirely. No fallback message, no error — they just don't render.

Suspected cause

The v2.1.139 changelog touched this exact code path:

- Fixed /usage weekly reset showing time of day instead of the calendar date - Fixed /usage Ctrl+S hanging when copying the stats screenshot to the clipboard on Linux/X11

Looks like the date-format fix has a side effect that prevents the bar block from rendering under some condition.

Workaround

Downgrade to v2.1.138.

View original on GitHub ↗

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