[Bug] `/usage` panel bar graphs not rendering in standard 80x30 terminal dimensions

Status Fixed / completed
Reported on v2.1.119
Maintainer reply None cached
Activity 3 comments · opened Apr 24, 2026 · closed Apr 24, 2026

Bug Description
Your /usage panel has gotten to be very annoying in the last week or so: I can't seem to find _any_ terminal dimensions that make it simply render the bar graphs nicely. It was never a problem before. PLEASE make it look fine in an 80x30 terminal window.

I have to admit your CLI's tools "posture" around column width makes me grumpy ... It doesn't feel like it treats 80 characters as "enough". For claude --help to look nice I have to have exactly 92 columns or more. That's just annoying.

Claude Opus 4.7 and the whole model degradation thing has been such a s--tshow. I really like your mission and principled stands against bullies -- but PLEASE get Claude Code and your infra TIGHT and CORRECT as soon as you can. I don't want new features. I want to know that it is SOLID. PLEASE!

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.119
  • Feedback ID: 135bffb2-7639-4153-9512-1eddbda21909

View original on GitHub ↗

3 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/49523
  2. https://github.com/anthropics/claude-code/issues/48801
  3. https://github.com/anthropics/claude-code/issues/48135

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

xpe · 5 months ago

This is fixed for me as of Version 2.1.119. From the release notes in Claude Code (the /release-notes command):

- Fixed /usage progress bars overlapping with their "Resets …" labels
github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.