Weekly account usage

Open Dashboard → Weekly account usage, or select an account in Accounts and choose Weekly account usage (u). Both views use the same components in the TUI, web console and native applications.

For Claude, the report groups recorded native usage by repository, conversation and model. It includes input, output, cache reads, cache creation and subagent tokens. Repeated streaming updates and repeated host scans do not add usage again. Available records survive a later failed scan and conversation deletion; removed projects are outside the current project scope. The ledger retains 91 days of numeric metadata and identifiers, never prompts, responses or paths.

The current period follows the account's officially reported weekly reset and duration. If the provider does not report a reset, the report explicitly uses a rolling seven days. A stale quota sample is marked stale. Native message timestamps select the period exactly; UTC calendar-day summaries cannot establish the beginning of a subscription week.

Subscription quotas are provider-weighted, and the provider does not expose a per-task breakdown of that percentage. The report therefore shows observed tokens, not a claim that one task spent a particular percentage of a paid subscription. Row percentages refer only to recorded tokens. Usage from other applications, missing native files, bounded/truncated scans and ambiguous copies remain incomplete. Copied histories across known accounts are excluded from account attribution; moving a transcript is not evidence of a new charge. Existing Codex daily project totals remain available, but this first account-level collector does not yet attribute Codex or Antigravity usage records.

The authenticated endpoint is GET /v1/accounts/usage-breakdown. Optional accountId, cursor and limit select an owned account and a bounded detail page. There are at most 100 accounts and 100 detail rows per requested page; default detail size is 30. The read queues at most two existing read-only host activity commands. Clients receive summaries, not native transcripts or the complete ledger. Account and project ownership are checked independently. No history is added to /v1/state.

The operator MCP catalog exposes this endpoint through controller_operations and controller_request; the Control Room uses the same owned operation. Host results may attribute only native account/conversation tuples authorized by that activity command. Ordinary project agents cannot read another account's global history.