35 lines (27 loc) · 1.53 KB

summary

Usage tracking surfaces and credential requirements

read_when

You are wiring provider usage/quota surfaces

You need to explain usage tracking behavior or auth requirements

title

Usage Tracking

Usage tracking

What it is

Pulls provider usage/quota directly from their usage endpoints.
No estimated costs; only the provider-reported windows.

Where it shows up

/status in chats: emoji‑rich status card with session tokens + estimated cost (API key only). Provider usage shows for the current model provider when available.
/usage off|tokens|full in chats: per-response usage footer (OAuth shows tokens only).
/usage cost in chats: local cost summary aggregated from Bitterbot session logs.
CLI: bitterbot status --usage prints a full per-provider breakdown.
CLI: bitterbot channels list prints the same usage snapshot alongside provider config (use --no-usage to skip).
Control UI: “Usage” section under Context (only if available).

Providers + credentials

Anthropic (Claude): OAuth tokens in auth profiles.
GitHub Copilot: OAuth tokens in auth profiles.
Gemini CLI: OAuth tokens in auth profiles.
Antigravity: OAuth tokens in auth profiles.
OpenAI Codex: OAuth tokens in auth profiles (accountId used when present).
MiniMax: API key (coding plan key; MINIMAX_CODE_PLAN_KEY or MINIMAX_API_KEY); uses the 5‑hour coding plan window.
z.ai: API key via env/config/auth store.

Usage is hidden if no matching OAuth/API credentials exist.