For AI coding agents

See what your CLI coding agent changed, as it happens

Running Claude Code in a terminal means the only visibility into what it's actually touching is a scrollback you half-read and a git diff you run after the fact — worse once you're running several sessions in parallel across tmux panes. Sarvak attaches to a live Claude Code session with zero setup, watches which files it's touching in real time, and shows a diff of exactly what changed, so you can review the blast radius without leaving your terminal workflow or waiting for a `git status` to remember to check.

How Attach works

• Zero-config detection. Sarvak's agent-helper CLI finds your live Claude Code session by reading the cwd field Claude Code already writes into its own session transcript — no flags, no manual "point it at this session" step.
• A live file-watch rail. As the agent reads and edits files, Sarvak shows a running rail of what it's touched, so you can see activity while the session is still going, not just the end state.
• A per-repo accent border. Once attached, the window gets a colored border keyed to the repo, stable across launches — a glance tells you which of several open windows is watching which session.
• A changes-only diff view. Toggle to Diff to see only what changed against git HEAD, with long unchanged stretches folded down to a few lines of context per side, and the gutter showing each line's real old-file/new-file position instead of renumbering everything from 1.

What it deliberately doesn't do

Attach is a viewer, not a controller — that's a design choice, not a gap to be embarrassed about. It doesn't send input back to the agent, approve or block tool calls, or pause/steer a running session; it watches and shows you the diff. It's also not an MCP server and doesn't implement the Model Context Protocol — the agent doesn't know Sarvak is watching, because the whole mechanism is reading the transcript Claude Code already writes and watching the filesystem, not a tool call the agent makes.

Today, zero-config Attach is built specifically around Claude Code's own transcript format. Support for other CLI agents (Codex, Aider, OpenCode) isn't built yet — each has its own session bookkeeping that would need to be read separately, so this isn't a "works with any CLI agent" claim.

Why not just use an AI-native IDE instead?

Cursor and Windsurf solve agent visibility by trying to be the editor — which works if you're willing to move your whole workflow into their window. Sarvak's bet is the opposite: stay in whatever terminal and editor you already use (tmux, nvim, ghostty, warp, VS Code), and let a featherweight, always-free viewer handle just the "what did it just do" question. Under 6MB, launches in under a second, no account.

Also useful for reviewing the rest of what an agent produces

A coding session doesn't just produce diffs — it drops Jupyter notebooks, JSON configs, generated Markdown docs, CSV exports, and log output along the way. Sarvak's full format list opens all of it natively, in the same window you're already using to watch the session.

FAQ