[BUG] WEB UI Plan Usage

Status Fixed / completed
Maintainer reply ✓ Yes — blois
Activity 9 comments · opened Mar 2, 2026 · closed Mar 6, 2026
💡 Likely answer: A maintainer (blois, collaborator) responded on this thread — see the highlighted reply below.

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?

related to
https://github.com/anthropics/claude-code/issues/30127
https://www.reddit.com/r/ClaudeCode/comments/1riz6fg/claudeaisettingsusage_now_showing_pro_subscription/

Bug Report: Plan Usage Limits Not Rendering on Settings > Usage Page

Date: March 3, 2026
Severity: High — directly impacts billing awareness
Affected Page: https://claude.ai/settings/usage

Summary

The "Plan usage limits" section (current session, weekly limits, progress bars) intermittently fails to render on the Usage settings page. When this occurs, only the "Extra usage" billing section is displayed, leaving users with no visibility into their plan consumption.

Reproduction Steps

  1. Navigate to Settings → Usage through the claude.ai app interface — Plan usage limits load correctly
  2. Refresh the page (F5 or browser refresh) — Plan usage limits disappear; only Extra usage section remains
  3. Navigate away and return through the app — loads again
  4. Refresh again — broken again, every time

Direct navigation to claude.ai/settings/usage via URL also consistently fails to load the Plan usage limits section.

Environment

  • Tested on three browsers: Google Chrome, Brave, Mozilla Firefox
  • All three produce the identical result
  • Two rendering engines affected: Chromium and Gecko
  • OS: Windows
  • Plan: Pro

Evidence

  • Screenshot 1: Page loaded correctly via app navigation — all usage bars visible
  • Screenshot 2: Same page after refresh — only Extra usage section displayed
  • Screenshot 3: Confirmed identical behavior on Brave browser

Why This Is Critical

  • Users with Extra usage enabled have no way to see their current consumption before it silently transitions to paid overage billing
  • No error message, loading indicator, or fallback is shown — the section simply does not render
  • The billing/upsell section (Extra usage) loads reliably every time while the usage tracking section fails
  • New users unfamiliar with the page layout may assume the Extra usage section is the entire page and purchase credits unnecessarily

Other Reports

  • Reddit post on r/ClaudeCode (March 3, 2026) by u/Character-Gas-5885 confirms the same issue: Plan usage not visible on web, only accessible via CLI /usage command. Notes it started after this morning's intermittent service issues.
  • Anthropic Status Page confirmed a usage reporting outage on Feb 26–27, 2026 — this may be a lingering frontend issue from that incident.

Requested Fix

  1. Ensure the Plan usage limits section loads reliably on every page load, not just via internal app navigation
  2. Display a loading state or error message if usage data fails to fetch — never show a blank page with only the billing section
  3. Do not render the Extra usage section without the Plan usage limits section — they must be tied together

What Should Happen?

Everything should show

Error Messages/Logs

Steps to Reproduce

Reproduction Steps

  1. Navigate to Settings → Usage through the claude.ai app interface — Plan usage limits load correctly
  2. Refresh the page (F5 or browser refresh) — Plan usage limits disappear; only Extra usage section remains
  3. Navigate away and return through the app — loads again
  4. Refresh again — broken again, every time

Direct navigation to claude.ai/settings/usage via URL also consistently fails to load the Plan usage limits section.

Claude Model

Other

Is this a regression?

Yes, this worked in a previous version

Last Working Version

0

Claude Code Version

1.0.123

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

_No response_

View original on GitHub ↗

9 Comments

github-actions[bot] · 6 months ago

Found 2 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/11102
  2. https://github.com/anthropics/claude-code/issues/30127

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

TheFunnyMan17 · 6 months ago

I found a "solution" in the form of enabling and then disabling Extra usage.

It'll glitch out for a moment, and I'm not sure if it works everywhere, but it's worth a shot.

Sidenote, it looks like the usage meter is spiking REALLY high for no reason. Two short (maybe ~10 total) messages, and it shot up to 95%.

blois collaborator · 6 months ago

Some issues are being tracked on https://status.claude.com/

Ariz992 · 6 months ago
I found a "solution" in the form of enabling and then disabling Extra usage. It'll glitch out for a moment, and I'm not sure if it works everywhere, but it's worth a shot. Sidenote, it looks like the usage meter is spiking REALLY high for no reason. Two short (maybe ~10 total) messages, and it shot up to 95%.

worked for me ty.

I also feel the usage meter is not working properly I dont know if its dependant on a certain model or a claude code issue

edit: nvm gets bugged again when you refresh

paralin · 6 months ago

I am seeing the same thing.

bcope · 6 months ago

I am also seeing the same thing and have been for much of the day. /usage is working on the CLI for me. macOS Ventura 13.5, Chrome Version 145.0.7632.117 (Official Build) (arm64).

jonlai211 · 6 months ago

same for me, there is no usage panel on usage web page

<img width="1879" height="619" alt="Image" src="https://github.com/user-attachments/assets/32c2b9cf-9cf9-4a17-bb39-cafd9f095e17" />

blois collaborator · 5 months ago

Should be resolved now.

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.