feat(usage): show remaining quota instead of used

[chrisdeeming]

Stacks on #9875 and includes its commits. Merge that first; this diff is the top commit only.

What Changed

• Limits bars and labels show what is left in each window instead of what has been used, on Usage → Limits and the /usage-limits panel, on web and mobile. Labels read "60% left".
• The even-spending hairline moves from time elapsed to time left, so a fill sitting on the line still means on pace and a fill short of it means ahead. The web tooltip reads in the same terms.
• Mobile's warning colours trigger on the remainder: amber at 30% left, red at 10% left.
• One shared helper does the inversion and rounding, with a test. Pace thresholds are unchanged.

Why

Codex reports remaining quota, and T3 Chat settled on the same framing. Showing the same number in the same direction everywhere removes a mental flip between products.

UI Changes

Web, before and after:

iOS, before and after:

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 (no motion changes)

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

Note

Add /usage-limits composer command and show remaining quota

• Adds a shared USAGE_LIMITS_COMMAND descriptor and isUsageLimitsCommand predicate so typing /usage-limits opens a local usage report instead of starting an agent turn.
• The server injects the command into provider catalogs only for opted-in clients and republishes it on usage-limit source changes in ws.ts.
• New collectProviderUsageLimits builds a timestamped report with native and pooled accounts; the web and mobile composers render it as a dismissible banner/card.
• Switches WindowBar and WindowRow from used percentage to remainingPercent (inverted, clamped, rounded) and moves the timeline marker to time-left.
• Behavioral Change: loadServerConfig now takes an opt-in argument; subscribeServerConfig filters source events by command coverage and may publish provider-status updates without a provider-registry event. LimitWindows now shows a reset countdown on every row.

^{Macroscope summarized 56127ea.}

---

Note

Medium Risk
Touches WebSocket subscribeServerConfig merging/deduping and send interception in composers; behavior is gated by client opt-in, but mis-sync could affect slash-command catalogs or when limits panels dismiss.

Overview
Usage limits now show quota remaining (e.g. “60% left”) instead of percent used on web and mobile Usage → Limits and in composer panels. Bars and tooltips use a shared remainingPercent helper; the pace hairline tracks time left in the window, and mobile warning colors key off low remainder.

Adds a client-handled /usage-limits slash command for providers that appear under Usage → Limits. Web and mobile thread composers build a live UsageLimitsReport from server config snapshots and show it above the composer (dismiss or clear on send / turn or pending-approval changes). Typing or picking the command does not start an agent turn when there are no attachments; New task blocks it with guidance to use a thread or Settings.

Clients opt in with usageLimitsCommand: true on subscribeServerConfig; the server injects the command into provider slash catalogs via withUsageLimitsCommands and republishes when limit-source coverage changes (zipped with provider status). Older clients that do not opt in keep unchanged catalogs.

Shared package adds UsageLimitsReport, command detection, report collection, and tests; user docs describe the composer flow.

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

[macroscopeapp]

🟡 Medium chat/ComposerUsageLimits.tsx:12

Native accounts with the same driver render the same providerLimitsLabel (and often plan), so users cannot identify which account owns a quota or reset-credit action. Because the instanceId branch ignores account.label, the instance identifier collected by collectProviderUsageLimits is lost; include that label in the native-account heading.

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

In file @apps/web/src/components/chat/ComposerUsageLimits.tsx around line 12:

Native accounts with the same driver render the same `providerLimitsLabel` (and often plan), so users cannot identify which account owns a quota or reset-credit action. Because the `instanceId` branch ignores `account.label`, the instance identifier collected by `collectProviderUsageLimits` is lost; include that label in the native-account heading.

[chrisdeeming]

Fixed on the base branch (#9875): the panel heading now shows the instance id whenever a native account has no display name and its id differs from the driver, so siblings of the same driver and plan read apart.

[macroscopeapp]

Sorry, I'm unable to act on this request because you do not have permissions within this repository.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a new /usage-limits workflow across web, mobile, shared contracts, and websocket streaming while changing default client capability negotiation and exposing quota/reset-credit behavior in the composer. Its cross-cutting runtime impact and unresolved medium-severity findings require human review.

Not approved because:

• 4 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.}

[macroscopeapp]

🟡 Medium components/ChatView.tsx:6678

clearUsageLimitsFor removes the open limits panel even when persistThreadSettingsForNextTurn or startThreadTurn returns Failure, so a message that never starts and spends quota still closes the panel. The same ordering occurs in onSubmitPlanFollowUp; defer both clears until after a successful startThreadTurn.

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

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

`clearUsageLimitsFor` removes the open limits panel even when `persistThreadSettingsForNextTurn` or `startThreadTurn` returns `Failure`, so a message that never starts and spends quota still closes the panel. The same ordering occurs in `onSubmitPlanFollowUp`; defer both clears until after a successful `startThreadTurn`.

[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 1ca3548. Configure here.}