trail

See what your coding agents did, folder by folder.

trail finds the sessions that Claude Code, Codex, OpenCode, Gemini CLI and Kiro CLI leave on your machine, files each session under the project it ran in, and shows the transcript next to the changes it made. Click an edit in the transcript to jump to its diff; click a diff to jump back to the step that made it. A Commits tab lists what landed in git while the session ran, with the commits that touch the agent's files first. Any session can be exported as one HTML file to share, and Stats show how your agents work across every project. And trail blame file:line tells you which session wrote a line, and which step and prompt. Lessons suggests rules for CLAUDE.md or AGENTS.md from what you keep correcting.

Each session opens with a trace: one tick per step, prompts tall, edits amber, failures red. Drag across it to move through the transcript. Press ⌘K (Ctrl+K) to search: it matches session names, and everything said and run inside every transcript. Pick a match to open the session at that step, with every other matching step marked on the trace; n and Shift+N step through them. / filters the sidebar by name, and j/k step between sessions. Bookmark a session or a single step, and leave yourself a note on either.

It’s a single static Go binary with an embedded browser UI (fonts included, nothing loads from the network). It only reads agent storage, never writes to it, keeps your notes in a file of its own, writes an export only where you save it, and makes no network calls unless you turn on related sessions, which talk to an embedding model on your machine.

Install

With Homebrew on macOS:

brew install veluribharath/tap/trail
trail -open

Or download the archive for your machine from Releases, unpack it, and run ./trail. Builds are published for macOS (Apple Silicon and Intel) and Linux (x86_64 and ARM64).

tar -xzf trail_*_darwin_arm64.tar.gz
xattr -d com.apple.quarantine ./trail   # macOS only: the binary isn't signed
./trail -open

With Go 1.24 or newer:

go install github.com/veluribharath/trail@latest

From source:

git clone https://github.com/veluribharath/trail && cd trail
make build

Run it

./trail            # http://127.0.0.1:7878
./trail -open      # and open the browser
./trail -list      # print sessions by folder and exit (or, with none, where trail looked)
./trail -search "flaky login"   # print matching sessions and steps, and exit
./trail blame cart.go:42        # the session and step that wrote a line, and exit
./trail -prices    # print the token prices used for costs, and exit
./trail -export c1 -o session.html   # write one session as an offline page, and exit
./trail -retro .   # print rules worth adding to CLAUDE.md or AGENTS.md for this project, and exit
./trail -notes     # print your bookmarks and notes, and exit
./trail -stats 30   # print the last 30 days in numbers (or -stats all), and exit
./trail -mcp       # an MCP server on stdio, so your agent can search past sessions
./trail -compare c1 c2   # print two sessions side by side, and exit
./trail recall "why is the db locked in tests"   # what the recall hook would add to this prompt, and exit

On a remote dev box, ./trail -host 0.0.0.0 and open the port from your laptop. Transcripts often contain secrets, so only do this on a network you trust (or tunnel the port over SSH instead).

Flag	Default
-host	127.0.0.1
-port	7878
-claude-dir	$CLAUDE_CONFIG_DIR or ~/.claude
-codex-dir	$CODEX_HOME or ~/.codex
-opencode-dir	$XDG_DATA_HOME/opencode or ~/.local/share/opencode
-gemini-dir	$GEMINI_CLI_HOME/.gemini or ~/.gemini
-kiro-dir	~/.kiro
-kiro-data-dir	~/.local/share/kiro-cli ($XDG_DATA_HOME/kiro-cli); ~/Library/Application Support/kiro-cli on macOS
-semantic	off; see Related sessions
-embed-url	http://127.0.0.1:11434 (Ollama)
-embed-model	nomic-embed-text
-prices	print the price table and exit
-export, -o, -redact	off; see Export a session
-no-notes	off: -export includes your notes and bookmarks
-notes	print your bookmarks and notes and exit; see Notes and bookmarks
-stats	off; a number of days, or all; see Stats
-retro	off; a project folder, or ; see

This is the beginning of the README. Read the rest at the original. Read the full README ↗