Hi, I pushed a new version with Cursor support. Cursor logs don’t include explicit thinking blocks or timestamps, so the player estimates both heuristically. Intermediate assistant messages are treated as “thinking” and timing is approximated for playback. Let me know if you try it!
Thanks for the feedback! Currently the tool only allows showing/hiding all thinking and tool blocks.
Would keyboard shortcuts to jump between thinking blocks or tool calls help? I could also add an option to highlight specific block/tools (e.g. Edit, Bash) to make decision points easier to scan.
good question. Currently, it works with standalone Claude code or Claude code via VSC extension (both terminal and chat).
Cursor stores JSONL logs, too, but no tool calls or timestamps. I'll add support for it soon; it will be a bit less informative, and playback pacing will be heuristic, but it's a good addition.
Ha, good question. Short answer: I often let Claude Code find it.
Sessions are grouped by the folder where you ran Claude Code (e.g. ~/.claude/projects/Users-<user>-<path>), so if you don’t run everything from the same directory, it’s usually easy to narrow down.
They’re also plain JSONL files, so grep works well if you remember part of a prompt.
That said, it might be nice for claude-replay to add a helper command to list or search recent sessions.
Good point. The reason I went with HTML is that you can expand tool calls, inspect prompts, jump around the timeline, etc., which would be hard to preserve in a video.
But you’re right that sharing in places like Slack could be easier with a video preview. Something to think about.
That’s a really interesting way to frame it — showing the flow of prompts and responses rather than just the final result.
I’ve mostly been using it for demos and sharing sessions with teammates, but the training / best-practices angle is a great point.
On navigation: you can already step through turns with the arrow keys or jump around the timeline, so you don’t have to sit through long generations. But I agree that smarter defaults (skipping or collapsing long runs) could make it smoother.
And the Loom comparison is interesting — I hadn’t thought about the workspace/permission side yet since this started as a small CLI tool for sharing sessions, but that’s a good direction to think about.
Ha, I like the claude2asciinema name!
I did think about asciinema-style output, but I wanted the player to expose the structured steps rather than just replay the terminal output. Supporting other agent CLIs could definitely be interesting.
Thank you, and fair question :) I’ve been experimenting with using Claude Code with hardware, where the interesting part is the tool usage and workflow, not just the final output. Screenshots and recordings made it hard to show, so the replay lets you step through the session and inspect what actually happened.