Quickstart
Install the CLI, connect your agent, and wire your first repository in under 10 minutes.
Concepts Overview
Learn how sessions, principals, commit trailers, and findings fit together.
Claude Code Integration
Connect Claude Code via hooks and start capturing sessions with full attribution.
CLI Reference
Explore every Terma CLI command — from setup and install to usage and sessions.
How It Works
Terma’s setup follows three steps that take you from zero to full attribution coverage.1
METER — Connect Your AI Tools
Run
terma setup to sign in and bind your coding agents. Terma hooks into Claude Code, Codex, Cursor, OpenCode, and other providers to capture sessions, token spend, and tool call events as they happen.2
LINK — Connect Your Repositories
Run
terma install from any repository root. Terma opens a pull request that adds git hooks, agent adapters, and a .terma.toml config file. Once merged, every commit stamped by an agent session carries a trailer that links the code change back to the session that produced it.3
WATCH — See Patterns and Act
Findings surface automatically: file-level burn maps show which parts of your codebase consume the most AI activity, retry loops flag repeated work, and attribution gaps highlight spend that isn’t tied to a person or project. Budgets and Slack notifications let you set guardrails before problems compound.
Supported Tools
Terma integrates with the AI coding tools and providers your team already uses.Coding agents: Claude Code, Codex, Cursor, OpenCodeProviders and gateways: OpenRouter, Anthropic SDK, OpenAI SDK, xAI, Vercel AI Gateway, Cloudflare AINew integrations are added regularly. Check the integrations section for the latest setup guides.