[Bug] Usage period selector is disabled without explanation in Limits view #16179

What happened

With Limits selected on the Usage page, the 1-, 7-, 30-, and 90-day period selector cannot be changed. The controls are visible but disabled, with no explanation of why. If only the day 7 is select-able then it should be conveyed in some way.

Diagnosis

This is client-side behavior in the installed build, rather than a failed request or an unsaved setting.

The Usage page passes disabled: s to its desktop segmented period control and mobile period picker; that same s selects the Limits view. The view renders live provider quota data in Limits mode, whereas the period selector applies to locally recorded historical usage.

The distinction may be intentional, but the disabled control has no contextual explanation and makes it appear broken. The page could either:

• hide the period selector while Limits is selected and state that limits are live/current; or
• retain a selectable history period if historical limit snapshots become supported.

Steps to reproduce

1. Open the Usage page.
2. Select Limits as the usage metric.
3. Try to select 1, 7, 30, or 90 days.
4. Observe that the period control is disabled on both wide and narrow layouts.

Version

0.0.46-nightly.20261005.2689

Environment

Linux arm64 (kernel 6.12.28), Node v26.8.2

Evidence

Installed client behavior:
- Desktop period control: disabled: s
- Mobile period picker: disabled: s
- The same s selects Limits rendering and changes the refresh label to
  "Refresh limits".

Server trace:
- ws.rpc.server.getUsageSummary completed successfully
- No error was recorded when Usage/Limits data was requested

Related issues

No matching T3 Code issue found. Existing issues about missing, duplicated, or incorrectly merged provider limit accounts are unrelated to the disabled period control.

Fix applied or workaround

No machine changes were made. Switching back to Usage makes the period selector available; Limits only displays the current provider quota snapshot.

Filed by

Codex (GPT-5) via t3 triage in your browser.• Opened https://github.com/pingdotgg/t3code/issues/new?labels=via-triage