# Terma

- [Terma: AI Activity Observability](https://docs.terma.ai/introduction.md): Terma connects your team's coding harnesses, providers, and repositories into one attributed view — tracking sessions, token spend, and change attribution.
- [Terma Quickstart: From Sign-Up to Live AI Tracking](https://docs.terma.ai/quickstart.md): Install the Terma CLI, connect your coding agent, and wire your first repository to start capturing AI activity across your entire team.
- [Set Up Your Terma Account, Projects, and Team Access](https://docs.terma.ai/account-setup.md): Create your Terma workspace, invite teammates, configure projects, manage organization settings, and get your team onboarded to the CLI.
- [How Terma Works: Sessions, Attribution, and Spending](https://docs.terma.ai/concepts/overview.md): Understand Terma's core model: how AI sessions are captured, attributed to people and changes, and how spend is tracked across providers.
- [What Is a Terma Session? Messages, Tools, and Cost](https://docs.terma.ai/concepts/sessions.md): A Terma session captures the full timeline of an AI coding conversation: prompts, tool calls, model responses, file edits, and token cost.
- [AI Change Attribution: Sessions to Commits and PRs](https://docs.terma.ai/concepts/attribution.md): Terma links AI sessions to git commits via commit trailers, so every merged change carries the sessions, tool calls, and cost that produced it.
- [Entitlement Portfolios: AI Cost Tracking Across Providers](https://docs.terma.ai/concepts/entitlements.md): Terma models each engineer's AI entitlement portfolio — subscriptions, metered keys, and prepaid balances — and tracks spend across all providers.
- [Connect Claude Code to Terma for Session Tracking](https://docs.terma.ai/integrations/claude-code.md): Wire Claude Code to Terma using project hooks in .claude/settings.json and OpenTelemetry export to capture sessions, tool calls, and spend.
- [Connect OpenAI Codex to Terma for Usage Tracking](https://docs.terma.ai/integrations/codex.md): Wire Codex to Terma via a notify entry and hooks.json to capture turn-by-turn activity, file edits, and token spend from Codex sessions.
- [Connect Cursor to Terma for IDE Session Tracking](https://docs.terma.ai/integrations/cursor.md): Wire Cursor and Cursor Agent to Terma using hooks.json for session and file events, with spend arriving via the Cursor Enterprise export.
- [Connect OpenCode to Terma via OpenTelemetry](https://docs.terma.ai/integrations/opencode.md): Wire OpenCode to Terma using a dependency-free plugin that emits OpenTelemetry from OpenCode events and forwards session and file activity.
- [Set Up OpenRouter with Terma via Broadcast](https://docs.terma.ai/integrations/openrouter.md): Point OpenRouter Broadcast at Terma's OpenTelemetry endpoint to track every routed model call — tokens, cost, provider, and session — across all the models your team uses.
- [Replay and Inspect AI Sessions in Terma's Dashboard](https://docs.terma.ai/dashboard/session-replay.md): Use Terma's session replay to step through every prompt, tool call, file edit, and model response in a coding session with cost and token context.
- [Codebase Burn Map: AI File Activity and Hotspot Findings](https://docs.terma.ai/dashboard/burn-map.md): Terma's burn map turns your repository into a living view of AI activity — revealing files with repeated reads, retry loops, and concentrated spend.
- [Team AI Activity Breakdowns by Person, Model, and Provider](https://docs.terma.ai/dashboard/breakdowns.md): Pivot Terma's attributed AI activity by person, tool, model, provider, harness, or repository area to understand how your team works with AI.
- [Set AI Spend Budgets for Teams and Repositories](https://docs.terma.ai/dashboard/budgets.md): Configure AI spend budgets in Terma with soft Slack alerts and hard caps that stop sessions — scoped to teams, repository areas, or experiments.
- [Track AI-Assisted Changes in Production with Terma](https://docs.terma.ai/dashboard/production.md): Terma marks AI-assisted deploys and aligns before-and-after signals — outcome, loop depth, latency, and cost per unit — to each originating session.
- [Terma CLI: Query AI Activity from Your Terminal](https://docs.terma.ai/cli/overview.md): The Terma CLI gives you terminal access to sessions, usage, attribution, and harness management — with JSON output for scripting and pipeline use.
- [Install the Terma CLI on macOS, Linux, or via npm](https://docs.terma.ai/cli/installation.md): Install the Terma CLI using Homebrew, the install script, or npm. All methods verify the release checksum before installing.
- [terma setup: Sign In and Connect Your Coding Agents](https://docs.terma.ai/cli/setup.md): terma setup signs you in through the browser, selects your project, binds your identity, and connects Claude Code, Codex, and OpenCode to Terma in one command.
- [terma install: Wire a Repository for Commit Attribution](https://docs.terma.ai/cli/install.md): terma install wires a repository by writing commit hooks, agent adapters, and .terma.toml into a pull request — onboarding the whole team with one merge.
- [terma doctor: Verify Your Terma Setup End to End](https://docs.terma.ai/cli/doctor.md): terma doctor runs a scratch commit in a temporary worktree to verify that hooks, harnesses, and attribution are working — and shows the coverage percentage.
- [terma usage: Summarise Token Usage and Cost by Team](https://docs.terma.ai/cli/usage.md): terma usage sums token usage and cost over a time window, grouped by person, agent, model, or provider. Key flags: --since, --until, --user, --group.
- [terma session: List, Inspect, and Replay AI Sessions](https://docs.terma.ai/cli/sessions.md): terma session list, get, events, and git let you browse, inspect, and replay individual AI coding sessions from the terminal with full tool-call detail.
- [terma principal find: Resolve People Across AI Tools](https://docs.terma.ai/cli/principals.md): terma principal find resolves a name, email, alias, or ID to all principals (identities) a person holds across their connected AI tools.
- [Manage Agent Harness Connections with terma connect](https://docs.terma.ai/cli/harnesses.md): terma connect, terma disconnect, and terma harness status manage which coding agents export session events to Terma, with per-source control via --source.
- [terma spool: Inspect and Flush the Local Event Queue](https://docs.terma.ai/cli/spool.md): terma spool flush and spool status let you inspect and force delivery of queued session events that the background flush delivers to Terma with backoff.
- [Manage Your Terma Account and Machine Authorization](https://docs.terma.ai/cli/account.md): terma login, logout, whoami, org list, and update manage credentials, memberships, and binary updates from the terminal on a per-machine basis.
- [Manage Projects and Switch Context with terma project](https://docs.terma.ai/cli/project.md): terma project use selects the active project for all subsequent CLI commands, scoping usage queries, session lists, and harness connections to one project.