/usage command incorrectly shows 'only available for subscription plans' for Pro subscribers

Status Fixed / completed
Reported on v2.0.76
Maintainer reply ✓ Yes — blois
Activity 8 comments · opened Jan 7, 2026 · closed Jan 8, 2026
💡 Likely answer: A maintainer (blois, collaborator) responded on this thread — see the highlighted reply below.

Bug Description

The /usage command displays "only available for subscription plans" even when the user is logged in with a Claude Pro Account subscription.

This is a regression - /usage was working correctly until today (January 7, 2025) and suddenly stopped working with no changes on the user's end.

Steps to Reproduce

  1. Log in to Claude Code with a Claude Pro Account
  2. Verify authentication with /status - confirms "Login method: Claude Pro Account"
  3. Run /usage

Expected Behavior

/usage should display plan usage limits and rate limit status for Pro subscribers, as it did previously.

Actual Behavior

/usage returns: "/usage is only available for subscription plans."

Environment

  • Claude Code version: 2.0.76
  • Platform: macOS (Darwin 25.2.0)
  • Login method: Claude Pro Account (confirmed via /status)

Additional Context

  • The /status command correctly identifies the user as logged in with a Pro subscription
  • /usage does not recognize this as a valid subscription plan
  • This was working correctly until today, suggesting a backend or recent update issue

---
🤖 Generated with Claude Code

View original on GitHub ↗

8 Comments

jhw · 7 months ago

Confirmed; looks like something went bad about 1600 GMT today; please fix ASAP!

jhw · 7 months ago

Also the usage stats have disappeared from the web UI

yuruko · 7 months ago

hello. the limit % is returning null for the endpoints. a fix would be greatly appreciated!

pijim · 7 months ago

Having the same problem. If you're going to enforce limits, I need to be able to track it.

Rauxon · 7 months ago

Yup - definitely API behaviour change. I'd just written something yesterday to give me a pretty display of this info, came in this morning and it wasn't working.

Rauxon · 7 months ago

Looks to be working again.

blois collaborator · 7 months ago
github-actions[bot] · 7 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.