Show remaining usage / rate limit status in Claude Code

Resolved 💬 3 comments Opened Mar 5, 2026 by bsnead1220 Closed Mar 8, 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

As a Claude Code user working on long development sessions, I have no way of knowing how close I am to hitting my usage limit until it actually cuts off mid-session. This is a significant workflow problem — if I start building a complex feature and run out of tokens halfway through, I'm left with incomplete code and have to wait for the limit to reset before I can finish.

Proposed Solution

A visible indicator in the Claude Code UI or status bar showing approximate remaining usage for the current billing period
Ideally, a warning when I'm approaching the limit (e.g., "You've used 80% of your available usage")
At minimum, a way to query remaining usage via a command like /usage so I can check before starting a large task

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Developer tools/SDK

Use Case Example

I'm a Claude Pro subscriber using Claude Code in VSCode to build a web application. I start a new conversation to implement a multi-file feature — new backend routes, frontend components, database models, and wiring them all together. About 45 minutes in, mid-implementation with several files partially updated, Claude hits the usage limit and stops. I now have incomplete code across multiple files, no way to finish, and no idea how long until the limit resets. If I had seen a warning that I was at 80% usage before starting, I would have waited or scoped the work differently.

Additional Context

Power users doing active development sessions plan their work around available context. Without visibility into usage limits, there's no way to make informed decisions about when to start a new feature, when to split into a new session, or whether to wait for a reset. The current experience is equivalent to a gas tank with no gauge — you only find out you're empty when the car stops.

View original on GitHub ↗

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