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.
Hi 👋,
We use Claude Code a lot, and after a long session, there isn't a simple way to share exactly what happened with someone else. Prompts, responses, file edits, and tool calls all stay inside the terminal.
We built Claudebin to make that easier.
It's open source.
https://github.com/wunderlabs-de...
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?
Congrats on the launch, @vtemian. Simplifying session exports is key for developers. How do you plan to drive initial ?
Claude sessions often include sensitive data via tool output and file reads—what’s your philosophy for safe sharing (redaction, encryption, access control, retention/deletion), and which security/privacy tradeoffs did you deliberately make to keep the experience “one command” simple?
This would have saved me hours, but I’m concerned about leaking information. Is there an option to make it private by default? Also, could you implement an agent to pre-process and clean sensitive information from the exported data?
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.
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.
Hi there, big day!! :)
A few quick questions from someone embedding agentic coding into web/mobile apps (Next.js + React Native, often with Claude Code for backend scripts, migration tools, test gen, etc.):
Does it fully serialize everything useful? E.g., inline file read/write diffs (before/after views), bash command outputs (stdout/stderr), tool call results (web fetches, MCP responses), and any custom skills/hooks?
When resuming from the URL locally (via import?), how does it restore state? Does it replay the session into a new Claude Code instance, inject context/files/commands, or just load the viewer for reference?
For SaaS/team workflows: Can we embed selected ranges (e.g., a refactor block) as iframes in Notion/Linear/Confluence? How private are the URLs — random long slugs, password-protected, or self-hosted viewer option?
This tool is SO useful! Thanks a lot for building it and congrats on the launch 🚀
Hey Vlad, that pain of finishing a long Claude Code session and having no good way to show someone what actually happened is real. Was there a specific moment where a teammate asked what did you change or how did you get that working and you realized you had no clean way to show them?
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!
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?
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.
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:
