[FEATURE] claude --usage
Status Closed — not planned
Maintainer reply None cached
Activity 6 comments · opened Apr 26, 2026 · closed Jun 25, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Being able to query the usage of the subscription account used in the Claude binary would allow for the use of correct and reliable information for in-house tools.
Proposed Solution
claude --usage returns something like
output
> claude --usage
current_session: 17% - resets 12:20 (Europe/Copenhagen)
current_week: 23% - resets Apr 30 at 10pm (Europe/Copenhagen)
current_week_sonnet: 2% - resets Apr 30 at 10pm (Europe/Copenhagen)
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
I have an inhouse tool that wraps claude code
I would like to be able to create a slash command which simulates what claude code does when using /usage
Additional Context
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
5 Comments
For another use case:
I would like to use this to add the info to my i3 window manager statusbar.
/
usageexists but it's a dialog you open and dismiss — the information disappears the moment you close it. What I actually want is persistent, ambient visibility the way tools like oh-my-claudecode already do it:That single status line tells me session usage, weekly burn rate, time remaining, context window consumption, and tool call counts — without me ever leaving the terminal or opening a dialog. It's always there, always current.
Native Claude Code should offer something equivalent: a
--status-lineor similar flag that lets the shell prompt or tmux status bar pick up live usage data, plus a non-interactiveclaude --usageflag for scripting. Engineers on shared team/enterprise plans often aren't the billing owner and can't access the console — they just need to know "how close am I to the limit right now" without breaking flow.The dialog is fine for a deep-dive. The status line is what makes this actually usable day-to-day.
Strongly support this. The data is already there —
/usageinside a session proves it — so the missing piece is just a non-interactive entry point.My use case: I want to check remaining usage before kicking off a long agentic task, without having to spin up a full Claude Code session just for that one query.
claude --usagewould be a clean, scriptable solution.Closing for now — inactive for too long. Please open a new issue if this is still relevant.
For this purpose, I use
claude -p /usage. It works unlessCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICis set.