Usage & rate-limit tracking

Orca fetches usage for Claude Code, Codex, Gemini, OpenCode Go, Kimi Code, MiniMax, Grok, Antigravity, Cursor, and GLM Coding Plan and surfaces it in the status bar, so you know how close you are to a rate limit before an agent stalls.

What's shown

  • Current usage against the active account's plan.
  • Time to reset for 5-hour, daily, weekly, and Claude Fable weekly windows (where applicable).
  • A warning chip when you cross 80% of a limit.

How it works

Orca asks each provider for your usage over the network, using the login that agent already has or a key or session cookie you add in Orca Settings.

Claude usage polling

Settings → Accounts → Claude → Claude usage polling is on by default. Turn it off to stop Orca's requests to https://api.anthropic.com/api/oauth/usage, including manual refreshes, account switching, inactive-account previews, and refreshes from mobile or web clients. Turning it off cancels pending usage requests and removes their cached figures while retaining live terminal readings. A request already sent cannot be recalled.

With polling off, the meter uses Claude Code's status-line data: five-hour and weekly percentages and reset times. This requires a supported Claude Code version and Orca's status-line feed. Orca preserves a user-owned status line, so those sessions do not supply this feed. Without a reading, usage is unavailable until a terminal session reports it. Model-specific weekly windows, credits, and inactive-account readings require polling.

The persisted setting is claudeOAuthUsageEnabled: false to disable polling. It applies on the host running the agents, including a headless Orca server; configure each host separately. Hiding the Claude status-bar item controls visibility independently.

When polling is enabled, Orca uses the token from your existing Claude Code login. Triggers include:

  • Once the Orca window is active after startup, then about every 15 minutes while it stays visible and focused.
  • Bringing the window back to the front when the last check is more than 5 minutes old (sooner after a failed check).
  • Switching the active Claude account or the runtime it runs in.
  • Refreshing usage from the Usage popover or a Settings control that refreshes all usage, or changing OpenCode Go, MiniMax, or GLM Coding Plan usage credentials or settings. These refresh every provider, Claude included.
  • Expanding the account list in the status bar's Claude account switcher, which fetches your other saved Claude accounts. The list opens expanded when an account needs sign-in.
  • Orca Mobile or the web client connecting to this host or refreshing usage, which also fetches your other saved Claude accounts.

Multi-account accounting

The status bar always reflects the active account. Other configured accounts are visible in the account switcher with their own usage.

Usage roster

Click the usage segment in the status bar to open the Usage popover. It lists every tracked provider (icon · name · plan · soonest reset · per-window bars), sorted so the tightest limit is first. Use the header refresh control to fetch usage again.

  • Detailed — full bars, labels, and percentages for every window
  • Compact — only the tightest window per provider

Under Settings → Appearance, choose % used vs % remaining for how those numbers read.

Rows without live numbers show a short status instead: Loading usage…, not signed in, Usage unavailable, No usage data, or a provider-specific error. Claude and Codex rows can drill into account switching; Manage accounts opens Settings.

Mobile

On the companion app, open the host Accounts screen for the same switcher/usage readout. When Codex has earned rate-limit reset credits, spend one from that screen (see Mobile companion).

Estimated cost (Stats)

The Stats breakdown may show estimated cost for known model families (including Claude 5-class and Codex GPT-5.6 rows). Rows marked • inferred pricing use Orca’s local price table, not a live bill from the provider. Prefer the provider console for authoritative spend.