[Bug] /usage endpoint returns subscription-only error despite active subscription

Resolved 💬 21 comments Opened Nov 19, 2025 by KJ7LNW Closed Jan 8, 2026

Bug Description
/usage is only available for subscription plans.
But this is a subscription plan, so there is a problem with getting usage. Please fix it so I can see my usage!

Environment Info

  • Platform: linux
  • Terminal: vte-based
  • Version: 2.0.37
  • Feedback ID: 3d22633a-02f3-4ae2-a0fb-528976a71a80

Errors

[]

View original on GitHub ↗

21 Comments

github-actions[bot] · 6 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

BartaG512 · 6 months ago

I got this error too. I have a Pro subscription.
<img width="944" height="180" alt="Image" src="https://github.com/user-attachments/assets/7dc17e1a-eee8-445e-a90f-6bee41cfca1a" /> 2.0.76

lev-lb · 6 months ago

getting this as well on v2.0.74 (running in a Debian Trixie Docker container on Linux, installed via npm):

> /usage 
 Settings:  Status   Config   Usage  (tab to cycle)

 /usage is only available for subscription plans.

 Esc to cancel

despite CC clearly being aware of my subscription status (below is switching from Usage to Status tab):

> /usage 
 Settings:  Status   Config   Usage  (tab to cycle)

 Version: 2.0.74
 Session ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
 cwd: /work 
 Login method: Claude Team Account
 Organization: <redacted>
 Email: <redacted>

 Model: sonnet (claude-sonnet-4-5-20250929)
 Memory: user (~/.claude/CLAUDE.md)
 Setting sources: User settings

this usually starts happening if session sat idle for a while (neither human interaction nor CC doing anything).
i suspect temporary network hiccups during the idle period might be related, although at the time /usage was invoked CC could clearly talk to the mothership, as it just executed on some prompts.

kflili · 6 months ago

Both website and cli shows /usage is only available for subscription plans., seems some server or usage meter service error, v2.9.76, start this morning.
Max plan.
<img width="1342" height="532" alt="Image" src="https://github.com/user-attachments/assets/9df29605-44fc-47ac-80c4-cfe804a6170b" />

p-samuel · 6 months ago

Same here

KJ7LNW · 6 months ago

This isn't limited to the user interface. It also fails when directly querying the usage API. This is all I get for response:

// ./tools/query_usage.pl -v
{
   "extra_usage" : {
      "is_enabled" : false,
      "monthly_limit" : null,
      "used_credits" : null,
      "utilization" : null
   },
   "five_hour" : null,
   "iguana_necktie" : null,
   "seven_day" : null,
   "seven_day_oauth_apps" : null,
   "seven_day_opus" : null,
   "seven_day_sonnet" : null
}
mttbrln · 6 months ago

Also seeing this in the CLI and web app.

skhelladi · 6 months ago

I'm encountering the same issue.

Andre-Mygentic · 6 months ago

I'm encountering the EXACT same issue.
Version: 2.0.76
Login method: Claude Max Account

MacOS + Iterm2

Andre-Mygentic · 6 months ago

Guys, this has been open since November nineteenth. People depend on that command to properly schedule how they work with Claude Code. This is not a minor issue. It should be immediately addressed.

ptsoo · 6 months ago

Same Here

paris-ci · 6 months ago

@Andre-Mygentic That just means the rate limits aren't currently applied... Trust me I was at 99% usage since that @BartaG512 comment was posted, and I've been using Claude since. Very cool! :)
No extra usage removed

rupaut98 · 6 months ago

Same here

darshanjmarakana · 6 months ago

exact same issue... iterm2 macos , doesn't even show anything on browser claude.ai/settings/usage max 20x user...

arnaudgs · 6 months ago

exact same issue for me on macOS, I can't see usage

zestsystem · 6 months ago

Seeing this issue as well.

Jinwei-Tang · 6 months ago

Same here

d13g0 · 6 months ago

Also seeing this issue at my end:
Version 2.0.76
Login Method: Claude Pro Acct
on MacOS

aswwwanth · 6 months ago

Looks like it got fixed. I can see it both in the CLI and web UI now.

github-actions[bot] · 6 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.