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
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.
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!
@vtemian @balajmarius Great idea. This was needed.
Claudebin
@vtemian @ahmetardal Thank you!
Great product. This solves a problem I face daily. Like many, when sessions compact I lose so much decision making context. Question: Can this auto-save? Claude supports hooks, so maybe a pre-compaction trigger that auto publishes to Claude Bin? Personally, my pain point isn't necessarily forgetting to share a session it's just losing it before I get the chance.
Claudebin
@leonardkim that's a good suggestion, we are going to experiment with this and see how cleanly we can implement it.
If you’re feeling inspired, we'd absolutely welcome a PR. Would love to build this with you.
Hi @balajmarius ,
Saw ClaudeBin on Product Hunt — really like the “sessions deserve a URL” framing.
One thought: positioning it slightly as workflow memory or version control for Claude teams could make the long-term value even stronger.
Curious how you’re thinking about that direction.
Claudebin
@harsh_upadhyay10 thank you! the version control is our vision too.
@balajmarius Love that. Makes a lot of sense — especially as more teams rely on AI-assisted coding.
Looking forward to seeing how you evolve that layer over time.
BlocPad - Project & Team Workspace
This is such a useful tool for anyone deep into Claude Code workflows. The fact that it captures the full session context — file edits, bash commands, MCP calls — and turns it into a shareable URL is exactly what's been missing. I love that you can embed selected ranges in docs too, not just dump the whole thread. Really smart for code review workflows where the "why" behind changes matters as much as the diff itself. Quick question: are you planning to support any kind of session diffing, like comparing two Claudebin sessions side by side to see how approaches evolved?
Claudebin
@mihir_kanzariya not on our roadmap but that's a fantastic idea!
Congrats on launching @Claudebin — exporting full Claude Code sessions (threads + file ops + tool calls) into a clean, shareable URL solves a real dev pain.
Post-PH, you could lean into “AI coding audit trail” positioning and track how many exports get viewed by a second teammate — that collaboration loop might drive retention.