Usage & Metrics

Claudette surfaces three related but distinct views:

Composer usage meter — small battery indicator next to the mic button in every chat composer. Always visible for Codex / OpenAI / OpenRouter / Pi / Ollama / LM Studio sessions (driven by Claudette’s per-turn token records). For Claude-family sessions, the meter is greyed out until you opt in to the Claude Code Usage experimental toggle, at which point it surfaces real Anthropic subscription quotas.
Claude Code subscription panel — the deeper Settings > Usage view, gated by the same toggle. Shows session / weekly limits and resets.
Claudette metrics — local activity (workspaces, sessions, commits, slash commands). Computed from Claudette’s database; never sent off-machine.

Composer usage meter

The composer indicator picks a data source per backend:

Backend kind	Data source	Always-on?
Anthropic / Custom Anthropic	Anthropic OAuth Usage API (subscription quotas)	Off by default — gated by the Claude Code Usage toggle
Codex Native / Codex Subscription	Live Codex `account/rateLimits/*` quotas (Session 5h + Weekly) when available; falls back to local-aggregate tokens with a plain `Codex` label until the first rate-limits push lands	Yes
OpenAI API / Custom OpenAI / OpenRouter	Local-aggregate tokens + OpenRouter `/credits` balance when the active endpoint is OpenRouter	Yes
Ollama / LM Studio / Pi	Local-aggregate tokens; Pi OpenRouter models also show OpenRouter `/credits` balance	Yes

Local-aggregate data comes from the chat_messages.input_tokens / output_tokens / cost_usd columns Claudette already writes for every turn. Nothing leaves your machine for those backends.

Pi sessions record token usage and provider-reported cost at the end of each turn when Pi exposes it. For OpenRouter-backed Pi models, Claudette also polls OpenRouter’s account credits endpoint with the same OpenRouter key configured for Pi and silently falls back to local token totals if the credits call fails.

Claude Code subscription panel

The Settings > Usage panel shows your subscription type, rate-limit tier, and current consumption against your plan. Open it from the sidebar footer or via the /usage slash command.

This panel is gated by the Claude Code Usage experimental toggle (off by default). When the toggle is off, Claudette never reads your Claude Code OAuth tokens for usage data — they stay strictly in the keychain / .credentials.json for the claude CLI’s own use. Enable it in Settings > Experimental if you want the panel. Requires a Pro or Max plan with standard login (env-var auth tokens like CLAUDE_CODE_OAUTH_TOKEN lack the OAuth scopes the API needs).

Claude Code sign-in itself is separate and always available in Settings > Models. Usage credential failures reuse that same sign-in flow.

The data comes from the same usage API your Claude Code CLI hits. Claudette caches the result for 5 minutes to avoid hammering the endpoint, and backs off for 2 minutes if a fetch fails (e.g. a rate limit). To force a refresh, close and reopen the panel.

To dive into the full Anthropic-hosted dashboard:

Click Open in browser in the panel, or
Use the /extra-usage slash command.

Both deep-link to claude.ai/settings/usage. The browser session uses your existing Anthropic login, not anything Claudette is holding.

Parallel agents and your plan

Claudette can run multiple agents in parallel git worktrees, but Anthropic’s plan terms treat Pro/Max usage as “ordinary, individual” use. Keep parallelism conservative (1–3 agents) unless you’ve moved to API-key billing.

Claudette metrics

The Metrics view shows Claudette’s view of your activity — derived entirely from local data.

Dashboard metrics

Metric	Meaning
Active sessions	Sessions currently running an agent turn.
Sessions today	Sessions started in the last 24h.
Commits today	Commits authored across all workspaces today.
Additions / deletions (7d)	Lines added / removed across all workspaces in the last 7 days.

Per-workspace metrics

Each workspace gets its own card with:

Commit count and net additions / deletions on the workspace’s branch.
Latest session turn count.
Total input / output / cache tokens for the latest session, when the underlying CLI emitted them.

Analytics

The deeper analytics view exposes:

Repo leaderboard — workspaces ranked by activity over a configurable window.
Heatmap — session activity by day of week and hour of day, like GitHub’s contribution graph.
Turn histogram — distribution of turn counts per session.
Top slash commands — which commands you actually use, ordered by frequency.
Recent sessions (24h) — a session-dot timeline of the last day.

These are designed to surface your own patterns. There’s no telemetry; the queries run against your local database and never leave the machine.

Deleted-workspace summaries

Archiving a workspace doesn’t drop its activity from the metrics. Closed-out work still counts toward leaderboards and 7-day deltas, so the dashboard keeps an honest picture of recent throughput even after cleanup.

What gets queried over the network

Source	Data	Trigger
Anthropic usage API	Subscription, tier, token totals	Opening the Usage panel; cached 5 min
OpenRouter credits API	Total, used, and remaining credits for OpenRouter-backed sessions	Composer meter refresh; 5-min cadence while active
Local SQLite	Everything else	On view; never network

See Privacy for the full network-activity ledger.