What this integration does

Lore turns any Claude Code session into a URL your team can open in a browser. Run /lore:share from inside the session and you get a link to the full conversation (prompts, tool calls, diffs, images), rendered the way it played out. See how to share Claude Code sessions with your team for the complete walkthrough and comparison.

The integration is a Claude Code skill. There is nothing to build, no application to install in your IDE, and no API key to configure. If you can run a Claude Code skill, you can share a session.

How it works

From a terminal, run claude plugin marketplace add loredotlink/lore-plugin, then claude plugin install plugin@loredotlink.
Inside any Claude Code session, run /lore:share. The first use walks you through Lore sign-in; then the skill exports the thread and returns a lore.link/thread/... URL.
Paste the URL anywhere you collaborate: a PR description, a Slack channel, a Linear ticket, a Loom comment. The recipient opens it in a browser and sees the conversation in full.

Prefer automatic capture? Install the Lore desktop app or CLI and opt into the directories you want Lore to upload. You can browse and search captured sessions later at lore.link/threads.

What gets exported

Everything in the session that's worth sharing:

Every prompt and assistant turn, in order.
Every tool call the model made and its result.
Every diff applied during the session.
Every image attached to a turn.
Skill invocations, with their input and output preserved.

What doesn't get exported:

Local files outside the session. Lore never reads your filesystem.
Anything in the session if you don't run /lore:share. The export is opt-in per session.

Visibility

Each shared thread can be set to one of three modes:

Private, only you. Use this when you want a personal archive or you're not yet sure whether the thread is worth showing.
Workspace, visible to teammates with the same email domain. The default for team sharing.
Public, visible to anyone with the URL. Use this for outbound sharing (a PR on a public repo, a tweet, a job application).

Visibility can be changed at any time. Deleting the URL removes the underlying thread.

When to share a Claude Code session

Three patterns where teams have made sharing stick:

PR review. Paste the Lore URL in the PR description when the why is more interesting than the what. Reviewers see the alternatives that got rejected and the constraints discovered mid-session.
Incident response. When the fix lives inside a long Claude Code session, run /lore:share before closing it. The URL goes into the post-incident doc; three months later, anyone asking "why does this work this way" has a one-click answer.
Onboarding. Curated Lore URLs are closer to pair-programming with the original engineer than any document a teammate has time to write. New hires read how the team thinks, not just what it shipped.

For a longer treatment of these patterns, see Share Claude Code sessions with your team.

Pricing

The Claude Code integration is free. The Free tier covers thread uploads, public links that never expire, workspace membership, and the Skills tab. Workspace-wide thread sharing and the Review feature (beta) come with Team ($20 per seat / month, minimum 2 seats).

Existing Lore URLs keep working at your current tier until the period ends, even after a cancellation.