Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Expose EE usage and budget cap in statusline API similar to rate_limits [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#55007•Fetched 2026-05-01 05:48:40
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
mh-avantmh-avant
Participants
github-actions[bot]github-actions[bot]mh-avantmh-avant
Timeline (top)
labeled ×3commented ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Description The randomly appearing and disappearing message about EE quota usage isn't sufficient. People want to be able to display it in the same way that they present other information in the statusline. It'd be very helpful if that was made available in a way that is similar to rate_limits.five_hour, but returns the monthly usage + budget cap for the user so they can display it in whichever way they'd like (percentages, progress bar, just the value, etc).

Environment Info

  • Platform: darwin
  • Terminal: iTerm.app
  • Version: 2.1.123
  • Feedback ID: 71383dfd-ae99-4b9f-942a-6b64886a105a

Errors

[]

extent analysis

TL;DR

Exposing the monthly EE quota usage and budget cap through an API similar to rate_limits.five_hour could provide the needed flexibility for custom display.

Guidance

  • Investigate the existing rate_limits API to understand its structure and how it might be extended or replicated for EE quota usage.
  • Consider adding a new endpoint or property that returns the monthly usage and budget cap, allowing users to calculate and display the information as desired.
  • Evaluate the feasibility of providing the data in a format that can be easily consumed and customized, such as JSON.
  • Review the documentation and user interface to ensure that any new feature or endpoint is properly documented and accessible.

Notes

The solution may require changes to the backend API and documentation, and should be designed with flexibility and customizability in mind to meet the needs of various users.

Recommendation

Apply workaround: Implement a custom solution using the existing API, if possible, or wait for an official update that exposes the EE quota usage and budget cap in a usable format.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#database connection#vector store#embedding generation#cache error#pipeline error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [Feature Request] Expose EE usage and budget cap in statusline API similar to rate_limits [1 comments, 2 participants]