claude-code - 💡(How to fix) Fix Feature request: expose account usage limits (session/weekly %) in CLI [2 comments, 3 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#60674Fetched 2026-05-20 03:52:28
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×2
RAW_BUFFERClick to expand / collapse

Feature request

Please expose Claude Code account usage limits in local CLI metadata/logs.

Claude Code JSONL logs currently include per-message token usage, but not the account/session/weekly usage percentage or reset times shown on https://claude.ai/settings/usage.

It would be very useful if Claude Code exposed:

  • current session usage percent
  • weekly usage percent
  • reset timestamps
  • plan tier / relevant limit bucket
  • whether the values are estimated or authoritative

This would allow local status monitors (status line, external dashboards, tmux widgets, etc.) to work without browser automation against claude.ai.

The key ask

Please expose the same usage percentage and reset times shown on claude.ai/settings/usage through Claude Code CLI logs or a local command (e.g. claude usage --json, or as fields in the existing JSONL stream).

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING