Docs /

Usage quota chips

Next to the ctx chip, Claude Code and Codex panes show how much of your plan you have spent — 5h 38%, 7d 71% — with the same amber-past-70 %, red-past-90 % bands. Hover it for every window with its reset time ("resets in 4h 12m"). The number shown is whichever window is closest to biting.

The title bar shows the full picture once per agent, next to the window controls: the agent's logo, a meter for the 5-hour session window, then every window with its reset — 11% used 2h 4m · 65% used 3d 1h (session, then weekly; a Claude gateway spend limit adds a third). Each figure takes its own amber/red band; hover for the labelled breakdown. Claude Code does not report per-model weekly limits to its status line, so those can't be shown. A plan limit belongs to your account, not to a pane, so this chip merges every Claude (or Codex) pane across all workspaces: it shows the highest current reading, ignoring any window whose reset has already passed.

The numbers come only from files those CLIs already write on your machine: Claude Code hands them to its own status line (so the chip needs the status line enabled), and Codex records them in its session log, re-read about once a minute. TAO CODING never contacts a vendor API and never reads your saved credentials, so there is nothing to show for agents whose CLI keeps no local record — Gemini, Qwen, OpenCode, Cursor and amp panes simply have no quota chip. Neither does a Claude or Codex pane that has not taken a turn yet, a plain shell pane, or a pane too narrow for the chip.