Show HN: Claude-replay – A video-like player for Claude Code sessions
Posted by es617 3 days ago
I got tired of sharing AI demos with terminal screenshots or screen recordings.
Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps.
I built a small CLI tool that converts those logs into an interactive HTML replay.
You can step through the session, jump through the timeline, expand tool calls, and inspect the full conversation.
The output is a single self-contained HTML file — no dependencies. You can email it, host it anywhere, embed it in a blog post, and it works on mobile.
Repo: https://github.com/es617/claude-replay
Example replay: https://es617.github.io/assets/demos/peripheral-uart-demo.ht...
Comments
Comment by rahimnathwani 3 days ago
The ones I've used which can convert coding session histories into readable HTML are:
https://github.com/simonw/claude-code-transcripts (only works with Claude Code)
https://github.com/Dicklesworthstone/coding_agent_session_se... (supports many coding agents but the tui feels kind of clunky and it only exports one session at a time)
Comment by bestouff 3 days ago
Comment by es617 3 days ago
Comment by kami23 3 days ago
Comment by swaminarayan 22 hours ago
Comment by dbgrman 3 days ago
Comment by prideout 3 days ago
Comment by es617 3 days ago
But you’re right that sharing in places like Slack could be easier with a video preview. Something to think about.
Comment by zxspectrum1982 3 days ago
Comment by es617 2 days ago
Comment by andreagrandi 3 days ago
Comment by d4rkp4ttern 3 days ago
https://pchalasani.github.io/claude-code-tools/tools/aichat/...
It brings up a nice TUI for filtering and further actions. There’s also a —json flag so agents can use it as a CLI search tool to find context about any past work. There’s a plugin that provides a corresponding session-searcher agent that knows to use this tool to search sessions.
I have hundreds/thousands of past sessions and this has been a life saver; I can just ask the main agent, “use the session searcher agent to get the details of how we built the tmux-cli tool so we can add some features”.
Comment by es617 3 days ago
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.
Comment by minixalpha 3 days ago
Comment by ftkftk 3 days ago
Comment by dinkleberg 3 days ago
Comment by btown 3 days ago
Showing a colleague that flow, and the sequence of not just prompts but the types of Claude outputs to expect, all leading to Claude doing something that would have taken us a half day of work? As a linear video, rather than just a dump or screenshot of a final page? That could help to diffuse best practices rapidly.
OP - you might want to look at the kind of data model Loom used for this problem for videos in general, in terms of workspaces and permissions. Could make a startup out of this!
(Also as a smaller note - you might want to skip over long runs and generations by default, rather than forcing someone into 5x mode! A user of this would want to see messages, to and from Claude, at a standardized rate - not necessarily a sped up version of clock time.)
Comment by es617 3 days ago
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.
Comment by throwaway27448 3 days ago
Would this not be visible in a text dump without taking half a day to watch? What's/who's the benefit/benificiary of the realtime experience here?
Granted, I have friends who don't read but prefer visual stimulation. I don't think the overlap with people comfortable with code is very large at all.
Comment by btown 2 days ago
Slowing it down to show the back-and-forth, and to let the viewer absorb and internalize the techniques behind each "prod," is vital!
Comment by monkeydust 3 days ago
Comment by es617 3 days ago
Comment by iugtmkbdfil834 3 days ago
Comment by clkao 3 days ago
related: I made https://github.com/clkao/agentlore can aggregate logs across team, and sharable with permalink. the logs are processed by agentsview, which supports multiple coding agents.
Comment by 9wzYQbTYsAIc 3 days ago
Comment by es617 3 days ago
Comment by minixalpha 3 days ago
Comment by smy20011 3 days ago
Comment by crashabr 3 days ago
Comment by BloondAndDoom 3 days ago
Comment by es617 3 days ago
Comment by handfuloflight 3 days ago
Comment by simonw 3 days ago
Comment by aiaboratory 2 days ago
Comment by es617 2 days ago
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.
Comment by aiaboratory 1 day ago
Comment by aplomb1026 3 days ago