The fastest way to share a Claude Code session in 2026 is to run /share inside the session and send the URL. But that is not the only way, and it is not always the right one. This guide walks through every method engineers actually use, what each is good for, and where it falls down, so you can pick the one that fits.
The short answer
If you want a teammate to see the whole session, prompts, tool calls, diffs, and the reasoning between turns, the best way is to export it to a shareable URL with Lore's /share command. If you only need to show a single error or a few lines, a screenshot or a copy-paste is faster and fine.
The rest of this guide is the long answer.
1. Screenshots
Good for: a single error message, one diff, a quick "look at this" in chat.
Falls down when: the session is the point. Screenshots lose scrollback, truncate long output, and turn searchable text into an image nobody can copy from or grep later. Stitching eight panes into one PNG is the tell that you are using the wrong tool.
Screenshots are the right call for a glance and the wrong call for anything someone needs to act on.
2. Copy-pasting the transcript
Good for: pulling one prompt or one block of output into Slack or a doc.
Falls down when: you paste a whole session. Terminal formatting collapses, tool calls and diffs lose their structure, and the reader has to reconstruct what happened from a wall of monospace text. The context that made the session valuable, the order of steps and the reasoning between them, does not survive the paste.
3. Terminal recordings (asciinema and friends)
Good for: showing the live feel of a session, demos, and conference talks.
Falls down when: someone needs to read, search, or quote it. A recording is a video. You cannot grep it, link to a specific step, comment on a line, or skim it in fifteen seconds. It is great for showmanship and poor for reference.
4. Committing a transcript to the repo
Good for: a permanent record that lives with the code, for teams that want everything in git.
Falls down when: it is unstructured. A raw .txt or .md dump in the repo is searchable by grep, but it is not parsed, not linkable by step, and it bloats the repo. It also goes stale: nobody updates a transcript, and nobody reviews one in a PR.
5. Lore (/share)
Good for: sending the whole session to a teammate, your team, or the public as a structured, searchable URL.
How it works: run /share inside a Claude Code or Cowork session (or /share-codex inside a Codex session). The session exports to Lore and you get a URL. The full thread renders in any browser, with tool calls collapsible and code syntax-highlighted. From there it is:
- Searchable across your workspace, so the next person who hits the same problem finds it.
- Linkable from a PR, a standup note, or a DM.
- Commentable at the block level, so feedback lands on the exact step.
- Forkable with
/fork, so a teammate can continue the work from where it ended.
- Scoped to private, workspace, or public visibility, so you control who sees it.
The export is opt-in. Nothing leaves your machine until you run the command, and you can trim sensitive messages or change visibility before publishing.
Falls down when: you only need to show one line. For a single error, a screenshot is faster. Lore is built for when the session itself carries the value.
How to choose
| If you want to... |
Use |
| Flag a single error or diff |
Screenshot |
| Drop one prompt into chat |
Copy-paste |
| Show the live feel for a demo |
Terminal recording |
| Send the whole session to a person or team |
Lore /share |
| Let a teammate continue the work |
Lore /fork |
| Make a session findable months later |
Lore (searchable workspace) |
A practical starter
The next time you finish a Claude Code session that taught you something, run /share and drop the URL in your team channel with one sentence about what is in it. Do not write a summary. The thread is the summary, and the URL is the artifact. Sharing scales when it becomes the path of least resistance: one command, one URL, no doc to write.
Frequently asked questions
What is the easiest way to share a Claude Code session?
Run /share inside the session. It exports the full thread to Lore and returns a URL that renders in any browser, with prompts, tool calls, and diffs intact. For a single line or error, a screenshot is quicker.
Can I share a Claude Code session without making it public?
Yes. With Lore, exported threads support private, workspace, and public visibility. Private is only you, workspace is your team by email domain, and public is anyone with the link. You choose before or after publishing.
How do I share a Claude Code session with my whole team?
Set the thread's visibility to workspace when you share it with /share, then drop the URL in your team channel. Teammates on the same email domain can open and search it. On the Team plan, workspace sharing is org-wide and links are permanent.
Do shared Claude Code links expire?
On Lore's free tier, shared links expire after 3 days. The Team plan ($20/seat per month, minimum 2 seats) keeps links permanent. Pricing is current as of June 2026.
Can someone continue my Claude Code session?
Yes, with Lore's /fork. Forking generates an AI-distilled handoff prompt from the original session, conditioned on what the teammate wants to do next, so they can pick up the work in their own agent without re-reading the whole thread.