Quorum Terminal monitors Claude Code (Anthropic) and Codex (OpenAI) usage in real time. Open the Usage panel from the right dock to see the current quota window, a live burn rate, historical analytics, and per-terminal cost. Gemini (Google) is tracked too where its CLI exposes usage.
The live usage monitor
The monitor shows the quota windows reported by each provider, including the current Session window (typically 5 hours) and Weekly window (7 days) when they are available. It reads quota metadata from the provider's local CLI session data and updates the panel in place as your agents work. Reset timers show when each window refreshes, so you know exactly when capacity returns.
Providers do not always report every window. Quorum Terminal keeps those states honest:
an unavailable window stays blank, while a Session value inferred from local activity is
marked with ~. A reported weekly limit is never reused as a Session limit.
Burn rate and depletion
From recent activity, Quorum Terminal computes a burn rate — how fast you are consuming
the window — and projects when you will run out. The estimate reads as
tokens run out at HH:MM, giving you a clear horizon for the current session. The
projection moves with your real usage: heavier work pulls the depletion time earlier, and
quiet periods push it later.
History and cost
Beyond the live window, Quorum Terminal keeps historical analytics: a per-model distribution of usage and a monthly ledger that only grows — it never shrinks, so past months stay intact for review. Costs are shown as an estimate labeled API-equivalent: they approximate what the same work would cost at standard API rates.
Tip: API-equivalent figures are an estimate for awareness, not a bill. Your actual charges come from your provider plan, not from Quorum Terminal.
Per-terminal attribution
Usage and cost are attributed per terminal, so you can see which session or agent is driving consumption. When several agents run at once, this breakdown makes it easy to spot the heaviest workload and decide where to pause, resume, or rebalance work.
Attribution is best-effort: it is estimated live from each session's logs, so a freshly started terminal can read as unknown until enough history accrues.
Something off on this page? Tell us.