Telemetry push

Many agents can push their usage straight to your organization over OpenTelemetry. Nothing is installed on anyone's machine.

Claude Code

An administrator adds this to Claude Code's managed settings. Find your organization token under Settings in the web app.

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "https://ingest.tokencontroller.com",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer tc_org_…",
    "OTEL_METRICS_INCLUDE_REPOSITORY": "true"
  }
}

These settings send numbers and identifiers only. The ingest endpoint drops any event that carries prompt text.

Other agents

Codex CLI, Gemini CLI, Copilot CLI and Cursor Enterprise push to the same ingest URL with the same organization token. Each page shows that agent's settings.

What telemetry sees, and what it does not

Each telemetry event is one model call: tokens, cost, model, person, repository and the IDs of the session and message. It does not see the branch, the pull request or a summary. Organizations that only push telemetry get cost on projects, by repository. Adding the mod or the CLI puts cost on tickets.

When telemetry and a token entry describe the same session, they are joined by session and message ID and counted once.