What is captured
Event names, session and agent ids, tool names, durations, reduced file paths, the program a command ran, the model, tokens and cost.
Local firstNo accountNo cloud
AgentMuse watches your Claude Code sessions and turns them into a living, visual picture.
Watch agents as they work
Explore your sessions
Create and share highlights
14 days free, then $19 once. No account. No cloud.
macOS 11.0 or later. Universal: Apple Silicon and Intel. Signed and notarized, so it opens without a security warning.
What the first five minutes look like.
See how you build with AI.
Turn your Claude Code sessions into a living, visual picture.
Connect Claude CodeLet AgentMuse watch your coding sessions.
AgentMuse will watch coding sessions on this Mac, across all your projects, so it can turn your work with AI into a live visual picture.
You're all set!
Now go do some work in your terminal.
$ claudeThere it is!
Your first agent is working.
Every shape is a tool call. Every outline is a claim about how we know. Marks that stay are failures that really happened. Learn it once and you can read any session at a glance.
What it is doing
The four are exhaustive. A fresh failure crosses the eyes on top of the state rather than instead of it.
A tool call is open right now.
Nothing of its own is running, but something it spawned is.
Nothing open, nothing delegated.
It stopped. Drawn brighter than a live one: in a still frame the thing worth noticing is what completed.
A turn, a tool call or a command failed, a tool was denied, or an error was raised. The crosses above stay after the agent has gone.
What it is holding
The family is the silhouette, so it survives greyscale and needs no label. Open calls sit to the right. Settled ones trail off to the left, newest nearest, so the trail reads as something left behind rather than a queue waiting to run. A filled shape has settled; an outline has not, because a call that started and never resolved is a gap in the record, not an error.
A small circle. Looking at a file without changing it.
A square. Editing or creating a file.
A triangle. A command in a shell.
A circle. Handing work to another agent.
What it has already put down. Three calls settled, newest nearest the head.
Two calls open while four have settled. This is what a working agent usually looks like.
How well we know it
The one claim this product refuses to fudge. Solid is the rare positive mark, not the default.
The provider said outright who spawned this agent.
Nobody stated who spawned it. It was worked out, computed, taken from documented behaviour, or simply not known. It does not mean the agent is inactive or broken, and in a real capture it is nearly every agent.
The look your sessions are drawn in. Included in the application.
Clean, focused, and fast. Default world.
Privacy
What AgentMuse keeps is the shape of the work, not the work itself. The reduction happens at ingress, before anything reaches disk.
Event names, session and agent ids, tool names, durations, reduced file paths, the program a command ran, the model, tokens and cost.
Prompts, model responses, file contents, command output, and your email or account identifiers. A field nobody named is dropped.
In a SQLite file on your Mac. No upload, no telemetry, no sync. An export is the only way anything leaves, and you ask for it.
FAQ