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.
Congrats on the launch, @vtemian. Simplifying session exports is key for developers. How do you plan to drive initial ?
Congrats on the launch! Making Claude Code sessions shareable and navigable feels incredibly useful, especially for PR reviews and async collaboration. How do you handle sensitive data inside sessions, for example API keys, internal URLs, or proprietary code, before generating a public URL? Is there a redaction or review step to prevent accidental leaks?
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?