Skip to main content
Your coding agent can set up traceroot, look up these docs, work with your project from the CLI, and send its own sessions to traceroot.

Set up tracing

You need Node.js 20.12 or later and a Python or TypeScript/JavaScript application. If you don’t have a traceroot account yet, you can create one when you sign in. Paste this into Claude Code, Codex, or another coding agent, from the root of your repository:
Setup prompt
Your agent runs setup, shows you a sign-in link and code if it needs one, adds the traceroot SDK, and finishes with a link to your first trace. Setup never reverts your agent’s edits, so review them with git status and git diff. To run setup in your terminal instead, see Tracing. If you’re self-hosting, start with Self-hosted traceroot.

Skills

Skills teach your agent how to work with traceroot. Setup installs its own instrumentation skill, so you don’t need one to set up tracing. Install one with:
npx skills is a third-party CLI that needs Node.js 22.20 or later. The traceroot-cli skill expects the traceroot command, so install it with npm install -g traceroot-cli.

Docs MCP

https://traceroot.ai/docs/mcp lets your agent search and read these docs, with no API key. For your traces, use the CLI.

Markdown docs

For any page as Markdown, add .md to its URL. Requests that send Accept: text/markdown get Markdown too.
  • llms.txt lists every page. Start here.
  • llms-full.txt holds every page in one file, about 300 KB.
  • skill.md is a short guide for agents: setup, common mistakes, and where to look next.

The CLI

Your agent works with your project through the traceroot CLI: traces, detector findings, alerts, dashboards, evaluations, and SQL. Run these from the directory you ran setup in. Anywhere else, sign in with traceroot login and scope to a project first. Without a global install, replace traceroot with npx -y traceroot-cli@latest.
Without --fields full, traces get --json leaves span input and output null. Run traceroot <command> --help for every flag, and traceroot doctor to check your setup. Output and exit codes covers what scripts and agents can rely on.

Trace your coding agent

Plugins for Claude Code, Codex, and pi send your coding agent’s own sessions to traceroot, which is separate from tracing your application. Sessions can include your prompts, tool input and output, commands, and file contents. If you export TRACEROOT_API_KEY for a plugin, it also applies to anything else you or your agent start from that shell, and it takes priority over the key in a repository’s env file.

Next steps

Tracing

Run setup yourself, add the SDK by hand, and troubleshoot.

CLI

Work with traces, findings, alerts, and evaluations from the terminal.