The installer sets up tracing for one coding agent at a time. It installs a small Python package into its own virtual environment, stores your credentials, and registers hooks with the tool you name. This page covers the install on each platform and how to check that it worked.

​
Before you start

You need two things:
  • Your Atatus license key, from Settings then License key in the dashboard.
  • A project name that you choose. It groups the data and names the project in the UI.
You also need Python 3.9 or later and git or curl available on the machine.

​
Install on macOS or Linux

Run the installer with the argument for your tool. This example traces Claude Code:
Use the argument that matches your tool: antigravity, claude, codex, cursor, devin, gemini, copilot, kiro, opencode, or omp.

​
Install on Windows

Download the batch installer, then run it with the same argument:

​
What the installer asks you

The installer prompts for a few values. Pressing Enter accepts the default shown in brackets:
  1. License key. Required. There is no default.
  2. Project name. Required. There is no default, because the name is how your data is grouped.
  3. Endpoint. Press Enter to accept the default. Change it only if you are running Atatus on-premise.
  4. Content logging. Three separate questions covering prompts, tool details, and tool content. The defaults are covered in Privacy.
Re-running the installer repairs an existing configuration rather than skipping it. If you accept a default that you previously overrode, the override is removed. This is intentional, so a machine with the wrong settings can be fixed by installing again.

​
What the installer changes

The install touches two places on your machine: Nothing else on the system is modified, and no background service is installed. Traces are sent directly from the hook process when it runs.

​
Trace more than one tool

Run the installer once per tool. They share ~/.atatus/harness/config.json, so the second install reuses the license key and project name you already entered:
Do not install the standalone package for Claude Code while the Claude Code plugin is also installed. Both register hooks, both fire on every event, and every span is recorded twice, which doubles the token and cost figures. Pick one.

​
Verify the install

Use the coding agent normally, sending at least one prompt, then open the LLM page in Atatus. Your project should appear within a minute or two. If it does not, work through these in order:
  1. Confirm you are looking at the LLM page and not APM.
  2. Check the log for the tool at ~/.atatus/harness/logs/<harness>.log.
  3. Confirm the license key in ~/.atatus/harness/config.json is correct.
  4. Confirm the tool’s own config file contains the hook entries.
To see what would be sent without sending it, set ATATUS_DRY_RUN=true and use the tool. Spans are written to the log instead of being transmitted.

​
Update

An update reinstalls the package and re-registers every tool you have set up. It reuses your stored configuration, so you are not prompted again unless a setting has changed meaning. On macOS or Linux:
On Windows:
You can also run the copy already on your machine, which is at ~/.atatus/harness/install.sh (%USERPROFILE%\.atatus\harness\install.bat on Windows):
That copy downloads the current installer and hands over to it before doing anything else, so an old local copy still updates you with the current steps. If the download fails, it says so and continues with the copy you have.
An offline install, made with --wheel-dir, never reaches the network. It keeps using its local installer and updates from the wheels you point it at.

​
Next steps