Always show Claude Code, Codex, and Cursor usage in the footer

[felipeorlando]

Problem

The usage footer is scoped to the active session. App.tsx only passes the active provider when it is Claude Code or Codex, and RateLimitProvider only supports claude | codex. A Cursor session therefore removes the usage chips entirely, and there is no Cursor usage chip.

I want an opt-in setting that keeps Claude Code, Codex/GPT, and Cursor usage visible at the bottom regardless of which provider is active.

Proposed behavior

• Add a persistent Always show provider usage setting.
• When enabled, show usage chips for installed/configured Claude Code, Codex, and Cursor providers even when another provider is active.
• Keep the current active-provider-only behavior as the default.
• Add a Cursor chip with remaining usage/reset information from a supported source. If Cursor does not expose personal-plan usage programmatically, show a clear unavailable state or a link to the Spending dashboard instead of silently omitting Cursor.
• Keep refresh/backoff behavior provider-specific and preserve the existing compact footer/overflow behavior.

Do not scrape undocumented endpoints or reuse credentials outside their supported scope. Cursor's public docs currently direct personal users to the Spending dashboard; its documented usage API is admin-oriented.

Existing work checked

• Upstream issue Usage limit section refresh frequency and bugs in the UI hardbeat920/monocode#20 and PR Refresh usage footer on turn end and stop rotating Claude's OAuth token hardbeat920/monocode#26 cover refresh timing, retries, and Claude/Codex credential handling.
• Upstream issue Show token usage and estimated cost in the status bar hardbeat920/monocode#85 covers historical token totals and estimated API cost.
• Neither covers an always-visible multi-provider roster or Cursor quota visibility.

Acceptance criteria

• The setting persists across restarts.
• Starting or switching to a Cursor session does not hide Claude/Codex usage when the setting is enabled.
• Cursor is represented explicitly: real supported usage data when available, otherwise a truthful unavailable/dashboard state.
• Disabled setting preserves current behavior.