Telemetry

V1 Honesty: OffRouter routes delegated work. It does not replace your harness's primary model call.

Opt-in only

Anonymous usage telemetry is off until you enable it. offrouter init asks once on interactive installs. Non-interactive and CI runs never enable it silently. You can change your mind anytime:

offrouter telemetry status
offrouter telemetry enable
offrouter telemetry disable

Set DO_NOT_TRACK (any truthy value) to force telemetry off for that process, regardless of local consent. Consent still lives in ~/.offrouter/telemetry.json; config may declare a preference under [telemetry] enabled but a real consent decision (with an anonymous id) is always required before anything is sent.

What is sent

Field	Example	Why
`anon_id`	random UUID	Stable anonymous install id (not an account)
`event`	`command_run`	Event type (only this value today)
`command`	`doctor`, `init`, `install`, `route explain`	Which small set of CLI commands ran
`cli_version` / `node_version`	`0.6.0` / `v22.11.0`	Support matrix for regressions
`os_platform` / `os_arch`	`darwin` / `arm64`	Platform coverage
`is_ci`	`true`/`false`	Filter automated runs
`exit_code`	`0`/`1`	Success vs failure rates
`provider_id`	`anthropic`, `openrouter`	Which vendors people route through (never an account id)
`model_family`	`frontier-coder`, `fast-coder`	Logical family only — never a literal model id

What is never sent

Prompt text, previews, or digests
API keys, OAuth tokens, or any secret material
Config file contents or profile names
File paths, usernames, hostnames, or IP addresses stored by us
Exact model ids
Spend, cost, usage, or limit numbers
Routing explanations, reason text, or audit records

Endpoint

Events POST to https://offrouter.com/telemetry with a short timeout. Failures are swallowed — telemetry never affects CLI exit codes or prints to the terminal.