"Approaching usage limit" banner
Bug Description
The "Approaching usage limit" banner in Claude Code (CLI, installed via the official distribution, version 2.1.105 on darwin) has three related UX problems that together make it feel like aggressive upsell nagging rather than a useful warning.
Problem 1 — Triggers way too early.
The banner appears in Claude Code when roughly half of the weekly usage is still unused. A warning about "approaching" a limit is meaningless when the user is nowhere near it. The trigger threshold appears to be broken or intentionally set absurdly early.
Problem 2 — Dismissal doesn't persist.
Clicking the × closes the banner only for the current Claude Code session. Every relaunch of Claude Code brings the same banner back. The dismiss state is never written to disk (nothing in ~/.claude/ stores it).
Problem 3 — No way to disable it.
There is no settings.json key, no environment variable, and no CLI flag documented for Claude Code that suppresses the banner. Users have zero control over whether they see it.
Expected behavior in Claude Code
Banner should only fire when the user is genuinely close to the weekly limit (e.g. 85–90% consumed), not at ~50%.
Dismissing with × should persist across Claude Code sessions until the user actually re-approaches the threshold.
An opt-out should exist, e.g. hideUsageWarnings: true in Claude Code's settings.json, or an env var like CLAUDE_CODE_DISABLE_USAGE_WARNINGS=1.
Steps to reproduce in Claude Code
Use Claude Code on a Pro/Max plan until ~50% of the weekly quota is consumed.
Observe the "Approaching usage limit" banner at the top of the Claude Code TUI.
Click × to dismiss.
Quit and relaunch Claude Code — banner reappears immediately.
Impact
In its current state the banner is visually disruptive in Claude Code, reappears on every launch, and cannot be turned off. This feels like aggressive upselling rather than helpful UX. Please either fix the threshold, persist dismissals, or ship an opt-out setting.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗