What is TraceQuest?
TraceQuest is a local web app and command-line tool for finding, reviewing, and analyzing the session files produced by coding agents. It brings sessions from supported agents and machines into a searchable index that developers and their agents can use to investigate past work. The app can also monitor and manage runs, while the CLI provides search, insights, standups, and handoffs. TraceQuest runs on your machine, with no telemetry.
TraceQuest Features:
Unified Session Index: Index sessions from Claude Code, Codex, Cursor, OpenCode, Grok, Droid, and other supported agents, including sessions imported from other machines over SSH.
Session Search: Search across indexed sessions for errors, past fixes, and other details, with the same index available to your coding agents.
Run Insights: Review recurring failure causes, agent error rates, retries, loops, active time, and estimated spend, filtered by project, agent, machine, or time range.
Live Run Control: Watch an agent run in the app, send follow-up messages, start a run in a folder, or continue an earlier session.
Standups and Handoffs: Create a standup from recent sessions or prepare a handoff that gives a new run relevant context and commands for opening earlier sessions.
Session Exports: Compare two sessions side by side, export sessions as HTML or Markdown, or share them to a Gist or Hugging Face.
Local Analysis: Browse and analyze local session files without model calls; standup summaries and agent runs use the agent you have configured.
TraceQuest Benefits:
Reuse Past Fixes: Finding explanations and working solutions in earlier sessions can help prevent repeated debugging and give subsequent agent runs useful project context.
Spot Recurring Issues: Failure patterns and retry information make it easier to see which problems keep interrupting work and where investigation may be needed.
Understand Agent Work: Session timelines and activity metrics help you review what agents did and how much active time or estimated spend their work involved.
Keep Work Moving: A session handoff can carry relevant history into a new run, reducing the need to reconstruct context from scratch.
Keep Data Local: Local browsing and analysis without telemetry let you inspect session history without sending it to TraceQuest.
Use Cases:
Debug Repeated Failures: Search previous sessions when tests keep failing, then use an earlier run's diagnosis to investigate the cause and document a fix.
Review Agent Activity: Inspect a live coding run while an agent reads, edits, or tests files, and send a follow-up message from the app.
Prepare Team Updates: Turn yesterday's sessions into a project standup that summarizes progress, blockers, and next steps with links to the underlying sessions.
Continue Earlier Work: Give a new coding run the relevant parts of an earlier session, along with commands for reopening those sessions.
Compare Agent Runs: Review two sessions side by side when checking how different runs handled a task, or export a session to share or archive.

