I'm curious what people here use for sharing agent coding sessions with colleagues? I'm sure we can learn from each other, but there's no perfect tool.
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)
I would have made a "claude2asciinema", for geek points. Also an opencode version.
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.
I just added a Claude alias that calls Claude with flags wrapped in asciinema. Only annoying thing is that people have wanted video or gifs and the conversion has been annoying a few times. Will fix it later.
This is amazing for getting new team members onboarded with Claude Code processes and tools I use. Thanks for working on it. will give it a try tonight.
cool project!
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.
really need tools like this, show how powerful my skill is to my colleagues
Neat. Would be nice if I could easily drop the replayer into a slack thread. Maybe a video file would be better for that than an HTML file?
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.
Question: how can you find the exact session you are looking for, among hundreds of them? I had a look at my ~/.claude/projects/*/ and I couldn't even find my last session.
In your last session, use "/status" to show your session_id, then find your session file in "~/.claude/projects/[your_project]/[session_id].jsonl"
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.
This is great. Excellent for knowledge sharing sessions and internal trainings. Thank you for putting this together so my clanker doesn't have to!
I can’t say I understand why one would want this lol. Watching cc session replays doesn’t seem particularly useful. But the execution seems well done, so nice job!
I'm discovering new possibilities all the time with how Claude can work on a new type of task in our codebase and business more broadly. While a lot of this can be brought to the team by saying "encapsulate what you just did into a skill," sometimes it's as much about knowing what kinds of prompts to use to guide it as well.
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.)
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.
> 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.
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.
I thought the same about watching people play video games but that's clearly a thing! This might be useful for educating people on how to use these new tools, perhaps those not in engineering but product, UX, less familiar with CLIs.
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.
I think the main use case is training. I feel more and more confident with my prompts ( and what tasks I can safely pass to what models ), but it is sometimes hard to explain to anyone else what made me go a particular route. This may help, because a person can follow your intuition.
Very nice, thank you. This will come in handy for a scientific agent I am working on.
Thanks! That sounds like a great use case. If you try it with your agent, let me know how it works out.
Looking forward to try this with my students. Thanks!
Nice to see a AI coding tool that not (complete) vibe coded! Well done.
I don’t if I’ll ever need it but this is super cool
thanks!
Excellent share! Danke.
This is really nice.