PR review
Link the session in the PR description when the rejected approaches and discovered constraints explain the diff better than another summary.
Thread sharing
Share Claude Code sessions with your team
- Hand off work to a coworker.
- Pick up work across different harnesses.
- See how other people are using your skills and plugins.
For remote teams, engineers, and founders who have more terminal tabs than time.
Run /lore:share in your agent to share a thread.
# PagerDuty P1: CRM sync lag, firing for 6 minutes…
> /lore:share
Uploading session…
✦ Shared to Lore
Sev2: the CRM sync backed up and stalled every renewal task
ShareCreated Jun 30 · Updated 10d ago
9:06 AM
Fire: the CRM sync backed up and stalled every renewal task. PagerDuty P1: sync lag above threshold, firing for 6 minutes. Help me contain it, then fix it.
9:06 AM
Order: confirm the blast radius, contain it, then root-cause. Pulling the live state first.
Worked for 15s · 2 tool calls
Blast radius confirmed. Containing first: scale out and drain the backlog so the sync recovers, then the root cause.
INSIDE THE SESSION
One command.
FOR EVERYONE ELSE
One link.
How it works
From session to link in one command.
01
Do the work
Run your session in Claude Code, Codex, Amp, or Cowork like you always do. The agent already records the session locally, so there is no separate document to write up.
02
Share it
Install the Lore plugin and run /lore:share in Claude Code or Cowork. Codex uses /share-codex, the CLI uses lore export, and the desktop app can upload automatically.
Share
Automatically
Automatically
Share
Manually
Manually
03
Send the link
A teammate opens the full thread: transcript, summary, decisions, files touched. Public threads open for anyone, no account required.
Choose the right way to share the session.
For one error, a screenshot is often enough. For a local coding-agent session that someone needs to understand, search, or continue, preserve the full thread.
| Method | Sharing effort | Available in terminal | Full transcript | Privacy levels | Search threads | Team workspace |
|---|---|---|---|---|---|---|
| Claude native sharing | Low | No | Varies | Private, public | No | Limited |
| /export + file | Medium | Yes | Yes | No | No | No |
| Gist or paste | High | No | No | Unlisted, public | No | No |
| Lore | Low | Yes | Yes | Private, workspace, or public | Yes | Yes |
This comparison is targeted at people using Claude Code in their terminal, which doesn't have a native share option.
The difference
A paste is a moment. A thread is a record.
A link, not a paste.
Pasted snippets lose everything around them. A thread link carries the whole context: what was tried, what failed, what got decided.
Readable by humans.
Raw session logs were never written for readers. Lore renders every session like a document, with the reasoning front and center.
Alive after you send it.
A paste is frozen the second you hit enter. A shared thread stays searchable, linkable from PRs, and connected to the code.
Forkable, agent to agent.
Fork a thread into a fresh Claude Code, Codex, or Amp session; the next agent starts with everything the last one learned.
#eng-help · Tuesday 4:12 PM
Maya pasting what I've got, sorry for the wall
Grep
{"path": "/Users/dev/cairn/engineering",
"pattern": "splitAutomations",
"output_mode": "files_with_matches"}
Read
{"file_path": "/Users/dev/cairn/engineering/
services/billing-sync/src/splitAutomations.ts"}
Read
{"file_path": "…/src/splitAutomations.test.ts"}
Edit
{"file_path": "…/splitAutomations.ts", "new_st…+ 372 more lines that didn't fit
Frozen the moment it was sent. Unreadable, unsearchable, already out of date.
The same link
TODAY
Explains the PR.
TOMORROW
Answers the Slack question.
A YEAR FROM NOW
Onboards the next hire.
Team handoffs
Put the reasoning where the work already happens.
Slack and incidents
Send the same URL in a team channel or incident handoff. It remains a readable record after the chat scrolls away.
Choose who can read it
Keep a thread private, share it with your workspace, or make it public. Public threads open without an account; other links enforce their scope.
Continue instead of repeat
A teammate can fork an accessible thread into a fresh agent session with a distilled handoff tailored to what they want to do next.
Frequently asked questions
Sharing Claude Code sessions with Lore
How do I share a local Claude Code session?
Install the Lore plugin, run /lore:share inside the Claude Code session, choose or change its visibility in Lore, and send the returned link. Cowork uses the same command; Codex uses /share-codex.
What does a teammate see when they open the link?
They see the complete session in order, including prompts, assistant turns, tool calls, results, images, and diffs when present. Lore renders the raw agent log as a readable browser document.
Can I share a session without making it public?
Yes. Threads can be private, workspace-visible, or public. New shares follow your account setting, which defaults to workspace visibility when you belong to a workspace and private visibility otherwise. You can change a thread later.
Does the recipient need a Lore account?
Public threads open to anyone with the URL, with no account required. Workspace and private threads enforce their visibility scope, so the viewer must have the matching access.
Can a teammate continue or fork the session?
Yes. A teammate with access can fork a Lore thread into a fresh supported-agent session. Lore distills the source thread into intent-specific handoff context so the next agent starts from what the first one learned.
The best explanation of your work already exists.
It's the session where you did the work. Stop summarizing it from memory and send the thread instead.