GitHub - viktor-com/tracequest: Trace Intelligence for Claude Code, Codex, Cursor, OpenCode, Grok and Droid sessions.

GitHub

4 min read Original article ↗

TraceQuest

Follow your coding agents. Find what happened.

A local web app and CLI for the sessions your coding agents already write.

TraceQuest. Asked why the tests in csv-stats keep failing, an agent searches every agent's sessions, finds the cause in a Cursor Cloud run and writes the fix into AGENTS.md. The next run passes.

Try it in a minute   Watch the launch film (44 seconds, with sound)

Claude Code · Codex · Cursor · Droid · OpenCode · Grok · vktr · fx · DeepSeek Harness
MIT · runs on your machine · no telemetry · no account

What it does

Asked why the tests in csv-stats keep failing, the agent finds four sessions with the same ModuleNotFoundError and a Cursor Cloud run that explains it, then adds the fix to AGENTS.md.

Agentic analysis

Ask your coding agent why runs in a repo keep failing. With TraceQuest it searches every agent's past sessions, finds the cause (sometimes another run already worked it out) and writes the fix into AGENTS.md, so the next run starts with it.

tracequest search "No module named"

Sessions from this machine, a GPU box, a laptop and Cursor Cloud merge into one searchable index of 19 sessions from 6 sources.

One index

TraceQuest puts every coding agent's sessions in one index: Claude Code, Codex, Cursor, OpenCode, Grok and Droid, from this machine, your other machines over SSH, and Cursor Cloud. You can search it, and so can your agents.

tracequest find "errors:>0"
tracequest import ssh gpu

Insights: 16 of 82 tool calls failed, grouped by cause with missing module first; 0.3 hours of agent time, $1.64 estimated spend, 7 retries, and error rates for Codex and Claude.

Insights

It also keeps the numbers: which failures come up most, error rates per agent, retries and loops, active time and estimated spend. Narrow it to a project, an agent, a machine or a time range. It's all computed on your machine, with no model calls.

tracequest insights --refresh

A Claude Code run reads, searches and edits files live; a test fails, the agent fixes it, and a follow-up message is typed into the same view.

The app

There's an app too. Watch a run while the agent is still working, send follow-ups to runs you started from it, start a new run in any folder, or continue an earlier session. Run npm start and open localhost:7777; starting and continuing runs needs tmux.

A timeline of yesterday's 19 sessions becomes a standup: progress per project, one blocker that was fixed, and what to ship next, each line linked to its session.

What falls out

Some things come for free once the sessions are indexed. Yesterday's standup, written from the sessions by the agent you already use. A handoff that gives a new run the relevant parts of earlier sessions, with the commands to open each one.

tracequest standup --yesterday
tracequest handoff "No module"

Also in the box

The clips run on sample sessions written for them; in the analysis and standup clips the agent's replies are acted out. Costs are estimated from token counts and model prices, not billing data.

Try it in a minute

TraceQuest is open source (MIT), runs on your machine and sends no telemetry. You need Node.js 22.5+ and git. Paste this into your coding agent, in the project you want to look into:

Add the TraceQuest skill to this project and use it.
1. Clone https://github.com/viktor-com/tracequest.git next to this project (../tracequest).
2. Copy ../tracequest/skills/tracequest into this project's skills folder
   (.claude/skills/tracequest for Claude Code, or your agent's own skills folder).
3. Follow that SKILL.md: install TraceQuest, then find out what keeps failing in this
   project's past agent sessions and propose a fix for AGENTS.md.

To browse it yourself instead, run npm run demo in the clone and open localhost:7777 for two bundled sample sessions, or npm start for your own.

Where TraceQuest finds each agent's sessions
Agent Sessions read from
Claude Code ~/.claude/projects/
Codex CLI ~/.codex/sessions/
Cursor ~/.cursor/projects/
Cursor Cloud tracequest import cursor-cloud
Droid (Factory) ~/.factory/sessions/
OpenCode ~/.local/share/opencode/opencode.db
Grok CLI ~/.grok/sessions/
vktr (Viktor's fork of the Grok CLI) ~/.vktr/sessions/
fx (Vercel's coding agent) ~/.fx/sessions/
DeepSeek Harness ~/.dsh/sessions/
Another machine tracequest import ssh <host>

Nothing to install in the agents. tmux (runs) and Rust (a faster indexer) are optional; prebuilt tarballs for macOS arm64 and Linux x64 are on each release. Installation, imports and troubleshooting · sources and paths.

Data and network access

Browsing and analysis only read local files. TraceQuest sends no telemetry. It contacts other services only when you ask it to: sharing a session, importing remote sessions, or checking plan usage limits. Standup summaries and agent runs use the agent you have configured.

The server listens on localhost and has no login. Read the deployment guide and security notes before making it reachable from other machines.

Documentation · Contributing · Changelog · MIT