Meters, budgets and pace

Settings → Usage

• A ring per vendor and per custom bot, from each vendor's own count: the ACP turn total, or the HTTP response's usage block. /usage opens it.
• In is fresh input — what the model read for the first time. Cached is context served back from cache, named apart so a long chat does not read as millions of new tokens. Out is what it wrote. The total is In + Out.
• View Usage over this stretch by day, week, month, or all time. Plan usage limits show the weekly allowance where the vendor reports one; Latest context shows the last turn's context.
• Cursor is two monthly pools — Cursor Models (Composer / Cursor Grok) and Other Models (third-party API) — and shows as two rings.
• A turn is estimated at four characters a token only when the vendor sent no count. So far that is Cursor.

When there is no meter

The desk reads official meters only. A vendor without one, or one that is not answering, shows an unknown ring — not zero, not full. Nothing is guessed.

Budgets and pace

• Budgets per vendor.
• A weekly pace that tells you when you are ahead of it, before the bill does.
• Tokens are recorded per vendor and per chat. Preview and failed-before-prompt record none.

Settings → Watch

• Daily bank hands every watched bot a slice of its plan per day and carries forward what it did not spend, so a long Monday does not leave Sunday with nothing. Choose the watched bots. Click Daily bank to change who stays on it.
• Desktop notification for Watch notices, such as a send hold.
• /watch shows leftover, daily spend, and send holds. You set the pace.