Files
bot/docs/concepts/usage-tracking.md
zeekay 4bdc9ee3e4 chore: rebrand openclaw → hanzo-bot for bridge merge
Comprehensive rename of all openclaw references to hanzo-bot equivalents:
- Package: openclaw → @hanzo/bot
- Binary: openclaw → hanzo-bot
- Types: OpenClaw* → Bot*
- Env vars: OPENCLAW_* → BOT_*
- Android: ai.openclaw.android → ai.hanzo.bot.android
- iOS/macOS: ai.openclaw.* → ai.hanzo.*
- Swift modules: OpenClaw* → Bot*
- Plugins: openclaw.plugin.json → bot.plugin.json
- Paths: .openclaw/ → .hanzo/bot/
- URLs: github.com/openclaw → github.com/hanzoai
2026-02-26 22:36:01 -08:00

1.5 KiB
Raw Permalink Blame History

summary, read_when, title
summary read_when title
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

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 Hanzo Bot session logs.
  • CLI: hanzo-bot status --usage prints a full per-provider breakdown.
  • CLI: hanzo-bot channels 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).
  • 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.