feat: show provider usage limits with /usage-limits

[chrisdeeming]

What Changed

• Adds a /usage-limits slash command. It is offered only for providers that appear under Usage → Limits. Sending it opens the current model's limits above the composer, built from the same snapshot as the Usage page. Nothing is posted to the thread and no turn starts.
• Web renders it as a composer notice: the Usage page rows one size down, plus banked reset credits and the redeem action. It dismisses with the notice control, on the next send, or when the thread or model changes.
• Mobile renders it as a card in the slot above the composer, using the Usage page's account block in a dense variant with the same reset-credit control.
• The server advertises the command in each provider's slash-command catalog when limits exist for that provider.
• Usage → Limits fixes that surfaced while building this: every window now shows its own reset countdown instead of collapsing matching ones into one, mobile bar fills above 70% were transparent because the color tokens did not exist, and the redeem button reads "Use reset" on both platforms.

Why

Checking how much quota is left meant leaving the thread for Usage → Limits. A limits snapshot goes stale as soon as the next turn runs, so it belongs in the transient slot above the composer rather than in durable thread history.

UI Changes

Note

Since producing the videos below, the feature has been changed to not require sending /usage-limits as a message. Clicking it in the slash command menu instantly displays the usage limits.

Web, Claude:

claude_usage_web.webm

Web, Codex with a banked reset credit:

codex_usage_web.webm

iOS, Claude:

claude_usage_ios.mov

iOS, Codex with a banked reset credit:

codex_usage_ios.mov

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Built with Claude Fable 5.1 in Claude Code via T3 Code.

Note

Add /usage-limits command to show provider usage limits in chat composer

• Adds shared command recognition, coverage predicates, report collection, and catalog decoration logic in usageLimits.ts, plus a new UsageLimitsReport contract in providerUsageLimits.ts
• Server's subscribeServerConfig stream in ws.ts injects the /usage-limits slash command into provider catalogs only for clients that opt in via a new capability flag in the subscription payload
• Web and mobile connection runtimes enable the usage-limits command capability; ChatView.tsx intercepts a standalone /usage-limits prompt and opens a local report panel instead of starting a turn
• ChatComposer.tsx clears the command trigger and invokes the callback when /usage-limits is selected from the menu
• Mobile gets a new ComposerUsageLimits docked card and compact/dense modes for AccountLimits, ResetCredits, and WindowRow; WindowRow bar colors now use explicit red (≥90%) and amber (70–89%) instead of semantic classes
• Risk: WindowRow in UsageLimitsSection.tsx switches from semantic destructive/warning color classes to hardcoded red/amber, which may not match theme overrides; LimitWindows in UsageLimits.tsx no longer suppresses repeated reset countdowns for windows sharing a reset time

^{Macroscope summarized f370809.}

---

Note

Medium Risk
Touches WebSocket server config streaming and capability-gated catalog mutation; incorrect opt-in handling could advertise or hide the command for the wrong clients, but auth and turn dispatch are unchanged.

Overview
Adds a /usage-limits composer command that opens provider quota locally from the same snapshots as Usage → Limits—no agent turn and nothing posted to the thread. It is offered only when Limits has data for the selected provider.

Server & clients: Subscribers opt in with usageLimitsCommand on subscribeServerConfig; the server then injects the slash command into provider catalogs via shared withUsageLimitsCommands, and republishes when limit-source coverage changes (not on every quota tick). Older clients that do not opt in keep unmodified catalogs so they would still send the command to the provider.

Web & mobile: Thread composers intercept a standalone /usage-limits (typed or from the menu) and show a docked panel above the composer; new task on mobile blocks with guidance to use a thread or Settings. Panels track live limit data, dismiss on close, and auto-close when the thread/model/turn changes or a message is sent. Shared collectProviderUsageLimits builds the UsageLimitsReport; usage UI pieces gain compact/dense variants and small fixes (per-window reset labels, mobile bar colors).

^{Reviewed by Cursor Bugbot for commit f370809. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a default-enabled, cross-platform /usage-limits capability spanning provider catalogs, WebSocket streaming, shared contracts, and web/mobile composer state and UI. Its broad runtime surface, plus unresolved command-routing and stale-data risks, warrants human review.

Not approved because:

• 3 blocking correctness issues found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d841ed6. Configure here.}

[macroscopeapp]

🟡 Medium components/ChatView.tsx:8097

When /usage-limits is selected while the composer has an attachment or terminal/element context, ChatComposer treats it as an action-only command, removes the command text, and opens the limits panel; the non-prompt content is therefore left unsent. onUsageLimitsCommand is passed whenever limits are offered, unlike the typed-command path, which excludes composerHasNonPromptContent. Only provide this action callback when the composer contains no non-prompt content so the command remains sendable with its attachment or context.

🤖 Copy this AI Prompt to have your agent fix this:

In file @apps/web/src/components/ChatView.tsx around line 8097:

When `/usage-limits` is selected while the composer has an attachment or terminal/element context, `ChatComposer` treats it as an action-only command, removes the command text, and opens the limits panel; the non-prompt content is therefore left unsent. `onUsageLimitsCommand` is passed whenever limits are offered, unlike the typed-command path, which excludes `composerHasNonPromptContent`. Only provide this action callback when the composer contains no non-prompt content so the command remains sendable with its attachment or context.