Skip to main content
This guide takes you from a new account to your first agent session in Terma. You will create an organization and a team, install the terma CLI, set up your machine once, and verify that sessions are flowing.
1

Create your account

Sign up at terma.ai/sign-up with Google, GitHub, or an email address.Terma is in private beta. If you are asked to Enter your invite code, enter the code from your invite — for example terma-7kq4-m2xp. If an organization invited you by email, you don’t need a code.Then Name your organization — use your company name — and optionally invite your colleagues by email. You can do both later from Settings → Organization.
2

Create a team

On your organization’s home page, select Create a team. Give it a name, such as the group or product it covers, tick Development, and select Create team.Terma opens a setup guide, Bring your first session into view. Choose the path for coding agents — Claude Code, Codex, Cursor, Pi, etc. — and keep the page open: it listens for your first session.
Connecting a router such as OpenRouter, or another tool that exports OpenTelemetry? Choose Other instead. See OpenRouter.
3

Install the CLI

Every method verifies the release checksum before installing. Check that terma is on your PATH:
See Installation for every option.
4

Run terma setup

From any directory, run:
You run it once per machine. It walks you through everything:
  1. Sign in. Your browser opens on Authorize the Terma CLI. Choose your organization and select Authorize, then return to your terminal.
  2. Choose your agents — Claude Code & Desktop and Codex TUI & Desktop. Each choice covers the agent’s CLI and its desktop app.
  3. Choose the team you just created. If your organization has only one team, it is chosen for you.
Setup then points your agents’ telemetry at a relay on your machine and writes their machine-wide hooks. Nothing is written into your repositories, and git’s configuration is not touched. See terma setup.When it finishes, restart any agent that was already running so it loads the new configuration.
Setting up a CI runner or an ephemeral VM, with no one to sign in? Use a team server key instead: see Set up a machine with no browser.
5

Collect your repository

Your team’s collection policy decides which repositories are collected. Open Team settings → Data collection and check that your repository is on the list as host/owner/name — for example github.com/acme/api — or that the policy collects Every session. An empty list collects nothing.Only organization admins can edit the policy. While you’re there, turn on Stamp commits with the agent session if you want commits linked to the sessions that wrote them.
6

Verify the setup

From inside your repository, run:
doctor checks every link — sign-in, whether your team collects this repository (and the origin terma sees), hooks, agent export, and delivery to Terma. Every failure names its fix, usually terma setup. See terma doctor.
7

Start a session

Start a new agent session in the repository and give it a task. Within a minute or two, the setup guide shows First session received, and the session appears on the team’s Sessions page.
8

Bring your team

Invite your colleagues from Settings → Organization. Each of them installs the CLI and runs terma setup once on their own machine. There is nothing to commit or merge.
With commit stamping on, when your agent makes a commit, the commit message carries the session that produced it:

​
Next steps

Team overview

Spend, burn rate, and breakdowns for your team.

Account setup

Invite colleagues, set collection policies, and map identities.