Visr
Show HN: Agents ship diffs. Visr keeps trajectories
Last verified:
What is Visr?
Visr is a terminal transcription tool that records the full trajectory of an agent or command session inside your own terminal. Instead of only preserving the final diff or outcome, it captures every command, output, retry, and fix so the full troubleshooting path can be reviewed later.
It is designed around the idea that the process behind a result is valuable memory for future work. Visr turns a shell session into a transcript link that can be shared with teammates, future agents, or downstream workflows, making it easier to reuse what was learned during the session.
The tool fits naturally into AI-assisted development and terminal-based workflows. You can run Codex, Claude Code, Cursor, or plain commands inside visr shell, and Visr transcribes the session while you work.
Visr appears aimed at developers, agent builders, and teams that want to create reusable terminal memory. It is especially useful when you want to seed artifacts like CLAUDE.md, AGENTS.md, MCP servers, skills, evals, or runbooks from real work rather than from a post-hoc summary.
Visr pricing
Pricing model: Freemium
The website’s getting-started instructions show a Homebrew install command, brew install sourishkrout/visr/visr, followed by visr shell. The page does not describe free tiers, paid plans, seat-based pricing, or usage limits on this changelog page.
Visr pros
- Captures the full session trajectory
- Records commands and outputs
- Includes retries and fixes
- Works in your own terminal
- Supports Codex sessions
- Supports Claude Code sessions
- Supports Cursor sessions
- Works with plain shell commands
- Produces a shareable transcript link
- Transcript link appears in the status bar
- Prints a short summary on exit
- Easy to copy and open transcript links
- Preserves dead ends and false starts
- Useful as input for future agents
- Can seed docs, skills, evals, and runbooks
- Connects multiple sessions into a trajectory graph
- Turns troubleshooting into reusable memory
- Fits terminal-native workflows
Visr cons
- Requires running inside visr shell
- Depends on a terminal-based workflow
- Focused on transcription, not code execution
- Not presented as a general-purpose IDE plugin
- Value is highest only after you exit the shell
- Transcript sharing may be manual
- Not meant for non-terminal tasks
- Does not replace final diffs or source control
Frequently asked questions about Visr
What does Visr actually record?
Visr records the full trajectory of a shell session, including each command you run, the output it produces, retries, and fixes. The point is to preserve the entire path to a result rather than only the final outcome or diff.
How do I start using Visr?
The page says to install it with Homebrew using brew install sourishkrout/visr/visr, then start a transcribed session with visr shell. From there, you work normally in your terminal while Visr captures the session.
Can I use Visr with AI coding tools?
Yes. The page explicitly says you can run Codex, Claude Code, Cursor, or plain commands inside visr shell. Visr transcribes whatever happens in that shell session.
What happens when the shell exits?
When the shell exits, Visr prints a short summary and places the transcript link on its own line. The page says this makes it easy to copy, open, and share the transcript.
Why is a transcript better than a diff?
The page argues that diffs only show the final result, while the transcript preserves the retries, dead ends, and fixes that led there. That makes the transcript more useful as memory for future agents and teammates.
What can I use the transcript for later?
Visr says the transcript can become the raw material for downstream artifacts like CLAUDE.md, AGENTS.md, MCP servers, skills, evals, follow-up reviews, and runbooks. In other words, it is meant to be reusable operational memory.
Does Visr connect multiple sessions?
Yes. The page says one visr shell can span multiple agent sessions, and the transcripts can connect from one session to the next. Visr describes that as trajectories linking into a graph.
How is the transcript link surfaced during a session?
In v0.2.0, the transcript link appears in the terminal status bar as soon as transcription starts. That gives you an immediate reference to the live transcript while you work.
Who is Visr for?
Visr is aimed at developers, agent users, and teams that want to preserve terminal work as reusable memory. It is especially relevant for people building agent workflows or documentation from real session history.
Does this page list detailed pricing?
No. The changelog page gives installation instructions and usage details, but it does not list free tiers, paid plans, or subscription pricing. Based on this page alone, pricing is not specified.