[FEATURE]

Resolved 💬 3 comments Opened Feb 3, 2026 by pedromalla95-pixel Closed Feb 7, 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

I run Claude Code on Claude Max with Opus 4.5 and rely heavily on multi-agent workflows (Task tool dispatches, parallel agents). Each agent call consumes significant plan quota, and I have no passive way to know how close I am to my rate limit.

Currently, the only way to check plan usage is to:

  1. Stop what I'm doing
  2. Type /usage
  3. Navigate to the Usage tab
  4. Read the percentage and reset time
  5. Go back to work

This creates two real problems:

  1. Blind quota consumption. I dispatch a heavy agent (30-50k tokens) without knowing I'm at 85% usage. It fails or gets throttled mid-execution, wasting the work already done in that session and breaking my flow.
  2. Unnecessary self-throttling. Without visibility, I conservatively avoid expensive operations "just in case," even when I might have 60%+ headroom. I downgrade to Sonnet when Opus would be the right tool, or I avoid parallel agent dispatches that would be more efficient.

The status line exists precisely to surface this kind of at-a-glance operational data. Context window usage is already there — but context resets every session. Plan usage is the one that actually gates whether I can keep working today.

Proposed Solution

Add plan_usage fields to the status line JSON payload:

{
"plan_usage": {
"used_percentage": 44,
"remaining_percentage": 56,
"resets_at": "2026-02-03T23:00:00-04:00",
"tier": "max_5x"
}
}

This lets the status line script display it however the user wants — percentage, bar, countdown to reset — without any new CLI flags or commands.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗