clawdbot/docs/concepts/usage-tracking.md

summary, read_when

summary	read_when
Usage tracking surfaces and credential requirements	You are wiring provider usage/quota surfaces You need to explain usage tracking behavior or auth requirements

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: compact one‑liner with session tokens + estimated cost (API key only) and provider quota windows when available.
• /cost on|off in chats: toggles per‑response usage lines (OAuth shows tokens only).
• CLI: clawdbot status --usage prints a full per-provider breakdown.
• CLI: clawdbot providers list prints the same usage snapshot alongside provider config (use --no-usage to skip).
• macOS menu bar: “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).
• z.ai: API key via env/config/auth store.

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