[BUG] /usage doesn't work for Claude Team account

Status Fixed / completed
Reported on v2.1.118
Maintainer reply None cached
Activity 3 comments · opened Apr 23, 2026 · closed Apr 23, 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?

Something has changed, I'm using a Team account of 20$, and before I could use /usage to see the metrics of my tokens.
Now it tells me I'm not using a subscription account, but if I open Claude Desktop - settings I can see the metrics of /usage.

What Should Happen?

Show same information as in Claude Desktop. As before, the bars of how many tokens I have used in current session and how much I have left for the week.

Error Messages/Logs

Steps to Reproduce

Open a new CLI session, write /status to see that the Login method: Claude Team account, and then /usage should show you /usage is only available for subscription plans.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.118 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

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/41841
  2. https://github.com/anthropics/claude-code/issues/46882
  3. https://github.com/anthropics/claude-code/issues/40597

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

set92 · 5 months ago

I only had to /logout and login for it to work again

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.