Launching today
Claude Code runs in your terminal. Session data is stored locally, but not in a human-readable format. If the session contains useful context, refactors, tool usage, reviewing or sharing it isn’t straightforward. Claudebin lets you export a Claude Code session. It captures: - the full message thread - file reads/writes - bash commands - web and MCP calls It returns a URL with a structured, navigable viewer. You can link it in a PR, embed a selected range in your docs, or resume it locally.
Claudebin
Biker: Track, Maintain, Repair
@vtemian That's such a great tool! Is there any way to have an organization within my profile so I can share the sessions only with my team?
Claudebin
Hey everyone 🚀
I'm part of the team behind Claudebin, building this together with Vlad.
If you're curious about how and why we built it, I wrote a detailed article breaking it down here:
https://balajmarius.com/writings/making-claude-code-sessions-shareable/
Happy to answer any questions, whether it's product decisions, technical details, or the story behind it.
Designmodo
I’ve run into the problem where a long Claude Code session produces great results, but sharing the process with teammates is basically impossible without screenshots or messy summaries.
Having a resumable URL with the full thread + file operations makes a lot of sense, especially for PR context or debugging sessions. It feels similar to sharing a notebook or replayable dev session rather than just output.
Claudebin
@andrianv That’s exactly the pain we’ve seen too. Great output, zero trace of how you got there.
Creative Tim
Congrats! love this, sometimes, after 4-5 hours of chatting, i get a huge huge history and it is reseting the terminal. That's not a problem as i remember most of the flows, but other people don't know the reason of what i did or not did something. What i actually want is a way to "bookmark" some of the informations that are relevant from those long threads. And reapply them. Are you working on something like this?
Claudebin
@axelut Yes, we're building proper team features so you can save key moments, revisit them later, and share context easily with others. That’s very much on our roadmap.
For me the code writing part of my work has now almost fully shifted from actual writing to prompting. So it makes sense that I want to see other people's prompts along with the code. It's a great tool for sharing.
If you think about it, where before you would open a PR and add a bunch of notes for reviewers, now you can include the chat history and it gives you so much context!
This tool is SO useful! Thanks a lot for building it and congrats on the launch 🚀
Claudebin
@vouchy a lot of examples. Usually, it happens when I want to show something that touches the frontend side. I work on the backend side and we need to integrate together, both using Claude Code.
Check more details here https://balajmarius.com/writings/making-claude-code-sessions-shareable/