Doors
A door is a way token entries or telemetry reach Token Controller. Pick the ones that fit how your people and agents work; most organizations use two.
Browse the docs
Getting started
Attribute
Account
Reference
Doors by agent harness
| Agent harness | Doors |
|---|---|
| Claude Code | The Claude Code mod, session files through the CLI, telemetry push, the GitHub Action in CI. |
| Codex CLI | Telemetry push, and session files through the CLI. See Codex CLI. |
| Gemini CLI, Copilot CLI, Cursor Enterprise | Telemetry push. |
| Any other agent | The token entries endpoint: one call per session. |
| Usage you only have on paper | Manual entry and CSV import in the web app. |
Which door to start with
Telemetry push is the fastest way to cover a whole organization: an administrator sets it once in managed settings and nobody installs anything. It knows the person and the repository, so cost lands on projects.
The mod and the CLI add what telemetry cannot see: the branch, the pull request and the one-line summary. With them, cost lands on tickets, and agent managers review their token entries before they submit.
The GitHub Action and the token entries endpoint are for agents that run without a person: CI, cloud and support agents. Their token entries arrive automatically and never go on a token sheet.
Where file readers come from
The CLI reads session files with the open source ccusage adapters. Token Controller reads session files for Claude Code and Codex only; every other agent reports by telemetry or through the endpoint.