Launched this week
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?
Product Hunt
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.
@balajmarius love to read what you have in mind man, thank you so much for jumping in so quickly!!
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.
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/
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?
Claudebin
@agraciag yes, we are thinking to add settings to users, they will be able to control default visibility, create teams, add team members.
@balajmarius Sounds great, I will keep an eye for sure!
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.