Tracing for omp records each agent run as a trace. Because omp re-prompts the model after every round of tool calls, a single run usually contains several model calls, and one trace covers all of them.

​
Install

On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, copies a hook file to ~/.omp/extensions/atatus-tracing.ts, and registers that file’s absolute path in the extensions array of ~/.omp/agent/settings.json.
omp does not discover an extensions directory automatically, so the registration in ~/.omp/agent/settings.json is required as well as the file itself. The installer does both. If you copy the hook file by hand, tracing does not start until the path is registered.

​
What gets captured

omp produces a three-level tree, with each model call in the loop as its own span:
A single trace commonly holds several LLM call spans, because omp calls the model again after each round of tool calls. To see the cost of a whole agent run, look at the total across the trace rather than at any one span.

​
Where things live

Four lifecycle events are forwarded: before_agent_start, turn_end, agent_end, and session_shutdown. Spans are sent straight from the hook handler, so there is no separate collector or buffer service to run.

​
Uninstall

This deletes the hook file and removes its path from the extensions array in ~/.omp/agent/settings.json. Check both if you are verifying the removal by hand. See Uninstall for the full-wipe option.