Feature Request: Configurable usage warning threshold

Status Closed — not planned
Maintainer reply None cached
Activity 6 comments · opened Apr 1, 2026 · closed May 28, 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

Currently, Claude Code displays usage warnings at fixed thresholds (50%, 75%, 90%).

I'd like the ability to configure when the first warning appears — for example,
suppress notifications until I hit 80% of my weekly usage limit.

Use Case

When I'm well under my limit (e.g., 38%), the warnings are distracting and not
actionable. I only want to be notified when I'm actually close to running out.

Proposed Solution

Add a setting in settings.json such as:
"usageWarningThreshold": 80

This would allow users to set the minimum percentage at which warnings appear.

Current Behavior

Warnings appear at 50%, 75%, and 90% — hardcoded, not configurable.

Expected Behavior

Users can configure the threshold (e.g., only warn at 80%+).

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

6 Comments

schmelik · 5 months ago

I want to escalate this request.

Using VSC Copilot, I get a notification every prompt that I have used 50%.

<img width="832" height="152" alt="Image" src="https://github.com/user-attachments/assets/00aec9bd-886c-49e5-8784-b29a7657379d" />

The 51% -- shoot I have 49% left. I should be able to, at least, mute the notification until the next step.

But manually setting the notification would be better

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

Eloren1 · 3 months ago

Bump, it even works incorrectly, I have more than enough usage left, the week ends faster than tokens.

<img width="862" height="387" alt="Image" src="https://github.com/user-attachments/assets/cf17de98-3b78-4fe8-86bd-00841f2c0051" />

#55572 #50558

Eloren1 · 3 months ago

Marking this other requests as duplicates but then closing this one as inactive and asking to open a new issue...

danedwardsdeveloper · 3 months ago

I initially assumed this was deliberate upsell behaviour, but after upgrading to Max 20 (the top tier), the banner is still showing and now serves no purpose at all, since there is nowhere higher to upgrade to.

Current behaviour across the three surfaces:

  • Claude Code: banner reappears at the start of every session.
  • Claude web: banner is dismissable, but does not persist, so it reappears anyway.
  • Mobile: banner cannot be dismissed at all. Tapping it shows: "Your subscription was originally purchased on web. To upgrade your plan or buy usage credits, visit claude.ai from your browser." This is a dead end on two counts: there is no higher plan to upgrade to, and buying usage credits is only relevant near the end of a billing cycle, not at 75%. It also takes up roughly 15% of the vertical reading space.
  • All three surfaces: the banner nags users to upgrade even when no higher tier exists.

On the "helpful reminder" framing: I'm already monitoring usage closely, so the banner adds nothing there either. Usage credits would only be worth considering if I were close to running out, say 99%, not at 75%. More importantly, usage on Claude Code and usage on mobile are not comparable. A single repo cleanup task in Claude Code (removing redundant comments, for example) can use 5M+ tokens in one session. An entire mobile conversation, say comparing Austen's and Bronte's prose styles, barely registers by comparison. So "75% of weekly budget used" is not useful information on mobile specifically, and the banner just gets in the way of reading responses, which is the core function of the app.

Since the banner appears from roughly 75% usage until reset, this is not a brief nag but a persistent state covering about 2 days a week across all three surfaces, so it's something I notice constantly rather than occasionally.

Given the volume of related reports in this thread, it would help to get a response on whether this is intended behaviour for top tier accounts, or whether it's on a roadmap to fix.

<img width="414" height="896" alt="Image" src="https://github.com/user-attachments/assets/c3f2df8c-ef69-4a76-9048-9f191d75e5ed" />
<img width="414" height="896" alt="Image" src="https://github.com/user-attachments/assets/d8df393b-f464-4975-8f98-7182bcc7079c" />
<img width="846" height="330" alt="Image" src="https://github.com/user-attachments/assets/15e958b5-de8c-45fd-a17b-7ce4a9c4d0a7" />

github-actions[bot] · 1 month ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.