Claudebin
Export and share your Claude Code sessions as resumable URLs
Start new thread
Vlad Temian

Claudebin - Export and share your Claude Code sessions as resumable URLs

by
Claudebin
•
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.

Add a comment

Replies

Best
Vlad Temian
Maker
📌
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...
Temian Mihai

@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?

Alexandru Paduraru

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?

Balaj Marius
Maker

@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.

Balaj Marius
Maker

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.

Andrian Valeanu

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.

Balaj Marius
Maker

@andrianv That’s exactly the pain we’ve seen too. Great output, zero trace of how you got there.

bogdanmoldovean

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!

Raul Popadineți

This tool is SO useful! Thanks a lot for building it and congrats on the launch 🚀

Catherine Cormier

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.):

  1. 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?

  2. 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?

  3. 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!

Balaj Marius
Maker

Hi @cathcorm, thanks for the great questions!

  1. Everything Claude does is fully serialized, nothing is left out.

  2. 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

  3. 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.

Catherine Cormier

@balajmarius love to read what you have in mind man, thank you so much for jumping in so quickly!!

Ahmet Ardal

@vtemian @balajmarius Great idea. This was needed.

Balaj Marius
Maker

@vtemian  @ahmetardal Thank you!

Mykola Kondratiuk

Been running into this with Claude Code constantly - you lose the whole reasoning thread when you hit context limits and have to restart. The shareable session idea is useful. What's the approach for auth on shared URLs? Wondering about private context leaking if someone shares a session that had sensitive project details in it.

christian b.

Great idea! thank you!

12
Next
Last