Claudebin and Lore both turn a Claude Code session into a link you can send someone, so they look like the same tool at a glance. They are built for different jobs. Claudebin is a fast, public paste: drop a session in, get a URL, done. Lore captures the Claude Code, Codex, and Cowork sessions your whole team runs and turns them into structured threads that are searchable, permissioned, commentable, and forkable.
This is a short guide to the difference, and which one fits what you are actually trying to do.
The one-sentence difference
Claudebin publishes one Claude Code session as a public paste. Lore makes your team's coding-agent sessions a searchable, permissioned, reusable library.
If you want to show a single session to the internet quickly, a paste is the right tool. If you want your team to find, read, comment on, and build on the sessions behind your code, that is what Lore is for.
At a glance
| Lore | Claudebin | |
|---|---|---|
| What it shares | Claude Code, Codex, and Cowork sessions | A Claude Code session |
| Default visibility | Workspace for workspace members; private otherwise; public is opt-in | Public link |
| Searchable across a team | Yes, by meaning across the workspace | No |
| Comments and review | Yes, at the block level | No |
| Fork and continue the work | Yes, with an AI handoff summary | No |
| Team workspace | Yes, auto-joined by email domain | No |
| Skills observability | Yes | No |
| Agent access (CLI and MCP) | Yes | No |
| Cost | Free to start; Team $20 / seat / month | Free |
What Claudebin is good at
Claudebin does one thing well: it makes a single Claude Code session public fast, for free, with nothing to set up. If you hit a clever result and want to post it in a thread or a chat, a public paste is perfect. No account to view, instantly shareable.
Its limits follow from being a public paste. The link is public, so it is the wrong place for anything touching private code. It is one session at a time, with no way to search across the sessions your team has shared, no place for a teammate to comment on the exact step that matters, and no way to pick the work back up where it ended.
What Lore is good at
Lore is the home for your team's AI coding sessions: it turns every Claude Code, Codex, and Cowork session into a URL the whole team can read, search, and build on. The difference from a paste is what Lore does with the session after it has the link.
A coding-agent session is prompts, tool calls, files the agent read, diffs it produced, and the reasoning between turns. Lore parses all of that into a structured thread, then makes it:
- Permissioned by default, with workspace visibility for workspace members, private visibility otherwise, and public visibility only when you choose it.
- Searchable across your whole workspace, so the next person who hits the same wall finds the answer.
- Commentable at the block level, so review happens on the exact step that matters.
- Forkable, so a teammate can continue from where a session left off with an AI-distilled handoff prompt that carries the context forward.
- Reachable by agents, through the
loreCLI and a hosted MCP server, so your own tools can read and create threads.
You also get Skills observability: see how a skill actually behaved across real sessions instead of inferring from screenshots.
When to use which
Use Claudebin when you want to show one Claude Code session to the public, it is not sensitive, and you do not need it to be searchable or reusable later.
Use Lore when the work is your team's, when more than one person needs to find or build on it, or when the reasoning behind your code is the thing you want to keep.
Frequently asked questions
Is Lore a Claudebin alternative?
Yes, for teams. Both produce a link to a Claude Code session, but Claudebin is a public, one-off paste, while Lore captures sessions across Claude Code, Codex, and Cowork as permissioned, searchable, forkable threads for a whole workspace. If more than one person needs the session, Lore is the closer fit.
Can I keep a Lore session private?
Yes. Lore threads support private, workspace, and public visibility. New threads follow your account setting: workspace members normally start with workspace visibility, while users without a workspace or with the setting off start private. A Claudebin paste is public to anyone with the link, which is why it is best for sessions you intend to make public anyway.
Does Lore work with agents other than Claude Code?
Yes. Lore captures Claude Code, Codex, and Cowork sessions. Claudebin is built around Claude Code sessions.
Can my own tools read Lore threads?
Yes. The lore CLI (npm install -g @loredotlink/cli) reads threads as JSON, and a hosted MCP server at mcp.lore.link lets any MCP-capable agent list, search, fetch, fork, and create threads.
The short version
Claudebin answers "how do I put this one session on the internet?" Lore answers "how does my team find, reuse, and build on the sessions behind our code?" If you are posting a single public session, a paste is fine. If you are sharing the coding sessions your team runs to build software, that is what Lore is built for.