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.
@vtemian @balajmarius Great idea. This was needed.
Claudebin
@vtemian @ahmetardal Thank you!
AgentReady
Great idea! thank you!
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?
Thanks guys!
Claudebin
Hi @cathcorm, thanks for the great questions!
Everything Claude does is fully serialized, nothing is left out.
We send Claude the full markdown transcript of the conversation and ask it to read and summarize it, then wait for further instructions, you can see a sample transcript conversation + instructions here: https://claudebin.com/api/threads/I0karOj-vb/md
Yes, absolutely, you can mark a thread as unlisted, it will not appear in search or on the threads page, but anyone with the link can still access it, we are also working on team and user access controls, as well as password protection, these are on our roadmap for the coming weeks.
If anything is unclear or you would like to dig deeper, just let us know. Happy to help.
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.
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?
Product Hunt