Claudebin Turns Claude Code Sessions Into Links. Almost Everything Around That Is Unfinished (2026)

Anyone who has tried to show a colleague what Claude Code actually did during a long terminal session knows the problem. The history sits on your machine in a format nobody wants to read, and screenshots don't capture the tool calls, file edits and back and forth that explain how you got to the final result. Claudebin arrived in February 2026 promising to fix exactly that, and it finished fourth on its Product Hunt launch day with around 260 upvotes. The idea landed. The product, eight months on, still feels like a first draft.

This is an editorial assessment based on the project's public repositories, its documented setup process and feedback from its users. It is not a hands-on lab test.

The basics at a glance

What the shared page gets right

Credit first, because it's deserved. When Claudebin works, the output is genuinely nice. A published session becomes a URL showing the full conversation thread, file reads and writes, bash commands and tool calls, all laid out in a structured viewer with syntax highlighting. For a pull request description or a quick Slack message along the lines of "here's how I fixed it", that's a real improvement over pasting walls of terminal text.

There's also an embed option for dropping a session into documentation or a PR. It works, though only as a static display.

Getting it running is the first hurdle

Claudebin has two halves: the website where sessions live, and a Claude Code plugin that publishes them from your terminal. The plugin isn't distributed through a package manager. You clone the repository, install dependencies with Bun (not npm or yarn), then launch Claude Code with a plugin directory flag. The documented route also involves the "dangerously-skip-permissions" flag.

Experienced developers will cope. But a tool whose whole purpose is making things easier to share shouldn't ask people to switch off a safety prompt as part of setup, and the lack of a one step install narrows the audience further than the Claude Code requirement already does.

The trust question

Sign in is GitHub only. No email, no Google. For most of the target audience that's a minor point, since they already live on GitHub. The issue is who you're authorising. Wunderlabs has a website, but there's no public team page and no easily verifiable company details, and the only names floating around come from first names in Product Hunt threads. Combine that with the absence of any privacy policy or data retention documentation we could find, and cautious users have reason to pause before connecting their account.

Free, but with unanswered questions

Claudebin costs nothing and the MIT licence means anyone can inspect, modify or self host it. That's the strongest argument in its favour. What's missing is the fine print that free tools still need. How long does a shared session stay live? Is there a cap on how many you can publish? Is there rate limiting or a storage ceiling? The documentation doesn't say. For someone sharing the odd session, that hardly matters. For a team thinking about building a workflow on top of it, it's a dealbreaker until answered.

A read-only viewer in a collaboration pitch

This is the gap that hurts most. The session page is look but don't touch. You can't comment on a step, highlight a section for a teammate or search a long session for a specific command. Resuming a session is awkward and poorly documented. Team features, which users requested on Product Hunt, still aren't there: no organisations, no permission controls, no private team spaces.

There's no mobile or desktop app either. Honestly, that matters less than the original version of this review suggested; few people need to read terminal transcripts on a phone. The missing comments and team controls are the real story.

The repositories tell a familiar story

The web app lives at github.com/wunderlabs-dev/claudebin.com and the plugin at github.com/wunderlabs-dev/claudebin. The code is tidily organised, with separate areas for components, server actions, API routes and database migrations, so self hosters and contributors won't get lost.

The activity is the worry. Commits come in short bursts separated by quiet stretches, the contributor list is small and the issue tracker is thin. That pattern usually means a side project with limited bandwidth. It may well keep going, but nothing public promises that it will.

Why the score is 1.2

The rating isn't a verdict on the idea, which is good. It's a verdict on whether you can rely on Claudebin today. It works with Claude Code and nothing else, so Cursor or Copilot users get no value. Setup is fiddly and leans on a permissions bypass. Sign in requires trusting a team that barely identifies itself. Limits, retention and privacy are undocumented. And the collaboration features that would make it more than a pretty paste bin haven't shipped.

Worth trying if: you're a solo Claude Code user who wants a quick, readable link to drop into a PR, and you're comfortable reading the source before installing.

Skip it for now if: you need team controls, clear data policies or anything you'd want to depend on long term.

For more takes on tools, trends and the people behind them, browse the latest Icon Polls features and reviews.

Quick answers

Is Claudebin free?

Yes. It's free and open source under the MIT licence, with no paid tier. Usage limits and data retention aren't documented.

Does it work with tools other than Claude Code?

No. Claudebin is built only for Claude Code sessions.

Is it safe to use?

The code is public, so it can be inspected. But setup involves the "dangerously-skip-permissions" flag, login goes through GitHub, and we couldn't find a published privacy policy. Proceed carefully, especially with sensitive projects.