deeptracer
Register agents

Local agent debugger

Don’t debug the output.
Trace the cause.

DeepTracer reads Claude, GPT, and Cursor session logs on this computer and opens each run as an execution graph. You follow the branch that went off intent — not the last message the agent printed.

Register agentsGitHub

Runs on this machine. A hosted site cannot read your agent logs.

Why desktop

Claude, Codex, and Cursor write sessions to disk. Vercel or Netlify cannot open ~/.claude, ~/.codex, or ~/.cursor. DeepTracer has to sit next to those apps — first as a local server, then as a desktop app.

Who it reads
Claude desktop on this PC
GPT / Codex desktop on this PC
Cursor desktop on this PC

Only installed desktop agents are listed. Credentials and auth files are ignored.

How it works

  1. 01
    Register agents

    DeepTracer finds Claude, GPT, and Cursor desktop apps on this machine. You choose which logs to scan.

  2. 02
    Runs by project

    Recent sessions become runs, grouped by agent and working directory. Search and sort without uploading JSON.

  3. 03
    Follow the graph

    A run opens as a DAG. Nodes are what a step obtained, not which tool was called. Inspector shows the result; Review intent finds where it drifted.

What you see

The canvas is a map of the run. Sub-agents stay as branches. Repeated tools collapse into the thing they got — a pricing source, a file, a page — not Search ×4.

Orchestrator
Research
Vendor A pricing
Browser
Pricing table

Research obtained a source. Browser never got the table. That is the cause.

Start on this computer. Register the desktop agents you already use, then open the first run.

Register agents