Supported Agents

TokenTelemetry reads log files from the agents listed below. Detection is automatic — no configuration needed. Just run your agent as normal and TokenTelemetry picks up the sessions.

Coding agents

Autonomous agents

Hermes has a dedicated dashboard at /hermes — see Hermes Agent for details.

Detection notes

Claude Code

Reads JSONL session files from ~/.claude/projects/<dir>/. Captures input and output tokens, cost, tool calls, plan-mode output, reasoning blocks (with honest labelling if encrypted), and subagent delegation cards.

Codex

Reads session JSON from ~/.codex/sessions/. Captures tokens, tool calls, and reasoning steps including extended thinking when enabled.

Gemini CLI

Reads session files from ~/.gemini/. Captures token counts (input/output), cost, and the conversation trace. Note: Gemini CLI does not expose per-call cache-hit data.

Antigravity

Antigravity is Google's browser automation agent. TokenTelemetry reads its sessions from ~/.gemini/antigravity/ and additionally captures browser screenshots and Antigravity recording strips (thumbnail sequences from browser_recordings). See Artifacts.

Cursor

Cursor stores its chat sessions in ~/.cursor/ and VS Code's workspaceStorage/. TokenTelemetry merges sessions from both locations. Plans extracted from Cursor's /plan output are available in the Projects → Plans tab.

GitHub Copilot

Reads Copilot's chat session files from VS Code's chatSessions/ directory (inside the VS Code user data folder). Token counts and cost are captured where the session log includes them.

OpenCode

Reads session data from ~/.local/share/opencode/. Token counts and traces are captured; OpenCode children sessions are included in the relayed-session count (they are already counted in the parent session's token totals).

The data directory follows $OPENCODE_DATA_DIR / $XDG_DATA_HOME when set, and the database filename depends on the release channel the build came from: latest and beta use opencode.db, everything else uses opencode-<channel>.db (a Nix install on the stable channel writes opencode-stable.db). TokenTelemetry reads all of them, so switching channels doesn't hide your older sessions.

Cline

TokenTelemetry reads both the Cline CLI SQLite store and the VS Code extension's JSON task history, de-duplicating sessions that appear in both.

SmallCode

SmallCode writes traces into each project directory rather than a global home dir, so TokenTelemetry discovers them under the project paths it already tracks from other agents (and honors the TT_SMALLCODE_ROOTS env var for extra locations).

Pi

Reads one JSONL per session from ~/.pi/agent/sessions/<encoded-cwd>/. Each assistant turn carries per-request token usage (input/output, cache read + write, reasoning) plus the provider, model, and cost, so token, cost, reasoning, and model data are captured per message. Cost is recomputed per turn with TokenTelemetry's own pricing — mixed-model sessions bill correctly, and turns where Pi runs against Ollama (or another local endpoint) are priced by local electricity instead of API rates.

Hermes Agent

Hermes writes its state to ~/.hermes/ (or the directory pointed to by $HERMES_HOME). TokenTelemetry reads:

• sessions.db / session JSON for per-call token and cost data
• agent.log for per-API-call latency and cache-hit percentages
• skills/, memory/, and soul/ directories for the configuration pages
• Cron schedule files for the Schedules sub-page

Requesting a new agent

Don't see your agent? Open a GitHub issue with the agent name and its log file format and we'll add support.