Skip to main content
This guide walks you through everything you need to go from a fresh signup to live AI activity tracking. By the end, the Terma CLI will be installed on your machine, your coding agent will be connected, and your repository will be wired to stamp commits with session attribution — all in under 10 minutes.
1

Create Your Account

Sign up for free at https://dev.terma.ai/sign-up. No credit card is required. You can authenticate with GitHub, Google OAuth, or a standard email address.Once you’re in, Terma creates a default project for you. You can invite teammates and configure additional projects from the dashboard at any time.
2

Install the CLI

Choose the installation method that fits your workflow. All three methods download the same release and verify its checksum before completing the install.
Every installation method verifies the release checksum automatically before writing any files to your system.
Confirm the install completed successfully:
3

Set Up Your Machine

Run terma setup to sign in and connect your coding agents. This is a one-time step per developer — it opens a browser-based PKCE sign-in flow, selects your project, binds your identity, and connects any detected agents (Claude Code, Codex, OpenCode).
Terma walks you through each detected agent interactively. After setup completes, sessions from your coding tools will start flowing to Terma the next time you open an agent.
4

Wire Your Repository

From the root of the repository you want to instrument, run terma install. Terma opens a pull request that adds git hooks, agent adapters, and a .terma.toml configuration file.
Once that PR is merged, every commit an agent session touches will carry a trailer that links the change back to the session — for example:
Run terma install once per repository. Every engineer who has run terma setup on their machine is automatically covered.
5

Verify Everything Works

Run terma doctor to check the full chain end to end. Every check names what it verified, reports its status, and — on failure — tells you the exact command to fix it.
Terma also predicts your attribution coverage based on what’s connected, so you can see any gaps before they show up in your reports.
Run terma usage --since today to see token spend and cost as soon as your first session lands. No waiting — activity appears in real time.