Tracing for Claude Code records every prompt as a trace, with the tools it invoked nested beneath it. This page covers both install routes and the Claude Code specifics.

Before you start

Each route needs a different thing already on your machine: The plugin is written in shell, so jq builds every payload and curl sends it. Neither has a fallback. Install jq with sudo apt-get install -y jq on Debian or Ubuntu, sudo dnf install -y jq on Fedora or RHEL, or brew install jq on macOS.
The plugin setup checks for both commands and prints the right install command for your system before it changes anything, so you do not have to work this out from an error later.

Install with the installer

On macOS or Linux:
On Windows:
The installer prompts for your license key and project name, stores them in ~/.atatus/harness/config.json, and registers the hooks in ~/.claude/settings.json. Add --with-skills to also link the manage-claude-code-tracing skill into the current directory, so Claude can help you change the tracing configuration interactively.

Install from the plugin marketplace

Claude Code can also install tracing as a plugin. The marketplace lives in the same repository as the install script, so there is no second source to add:
The marketplace flow registers the hooks but skips the setup wizard, so it does not know your license key. Set the values yourself in ~/.claude/settings.json under env, or no traces are sent.
Add an env block with your credentials:
ATATUS_OTLP_ENDPOINT is optional. Set it only if you are running Atatus on-premise. The three logging values above match the wizard’s defaults, so leaving a flag out gives you the same result as setting it to the value shown.
Do not install the plugin and the standalone package at the same time. Both register hooks, both fire on every event, and every span is recorded twice, which doubles your token and cost figures. Pick one.

What gets captured

Claude Code exposes the widest set of hook events of any supported tool, so its traces are the most detailed:

Where things live

Sixteen hook events are registered: SessionStart, SessionEnd, UserPromptSubmit, UserPromptExpansion, PreToolUse, PostToolUse, PostToolUseFailure, Stop, StopFailure, SubagentStart, SubagentStop, Notification, PermissionRequest, PermissionDenied, PreCompact, and PostCompact.

Notes

A turn that you cancel before it finishes has no token data, because Claude Code reports usage only when a response completes. The turn still appears in the trace, marked as closed by a fail-safe, so you can see that it happened. Cancelling prompts is normal, so expect some turns to carry no cost.

Uninstall

Remove the hooks from ~/.claude/settings.json and leave everything else in place:
If you installed the plugin instead:
See Uninstall for the full-wipe option.