How to share a Claude Code session
Every way to share or export a Claude Code session in 2026, from the built-in share link and /export to transcript tools, Lore, Entire, and a sealed review with PatchArc, with what each one exposes.
updated 2026-08-22 · competitor pricing and claims checked 2026-08-22 · PatchArc facts as of 0.2.0
There are six ways to share what happened in a Claude Code session. They differ in what the other person receives (a link, a file, a repository branch, a review), what they can do with it, and what you might accidentally expose. Facts below were checked on 2026-08-22 against Claude Code's documentation and each tool's public pages.
1. Claude Code share links
Claude Code added session sharing in February 2026: a read-only view of a session, served from claude.ai. It is the lowest-effort option and the right one for "look at what it did" inside a team that already uses Claude. Limits: the view is read-only, it lives on Anthropic's site, and the transcript format is internal and changes between versions.
2. /export
/export writes the session to a text file you can paste anywhere. Transcripts are also stored locally as JSONL under ~/.claude/projects/... with a 30-day default retention (cleanupPeriodDays). Good for a quick paste into an issue; bad for anything long, because the reader gets the whole conversation with no structure.
3. Claude Code checkpoints
Checkpoints let you rewind code and conversation state. The documentation is explicit that they are not a replacement for version control and do not track files modified by bash commands. They are for you, not for sharing.
4. Transcript-to-HTML tools
Simon Willison's claude-code-transcripts renders a transcript as a static HTML page and can publish it as a gist. Local-only tools such as vigilo log every tool call an agent makes with no accounts and no network. Use these when you want a readable artifact you control, and when you are comfortable that the whole transcript becomes a document.
5. Session-sharing products
Lore shares a full transcript with private, workspace, or public visibility, and generates a fork prompt for the next session (Team is $20 per seat per month). Entire captures transcripts, prompts, files touched, token usage, and tool calls alongside every commit on a Git branch, with secret redaction before storage (MIT CLI; pricing not published). See PatchArc vs Lore and PatchArc vs Entire.
6. Share the review, not the transcript
PatchArc takes the opposite approach: do not share the conversation at all. Run the session inside an Arc; the observer records the commits the agent makes; you record decisions and risks in one line each; patcharc stop computes a six-section review and seals it into a signed capsule; patcharc share publishes a link after the cloud re-verifies the signature and hashes.
$ patcharc start --detach "Claude: migrate auth tests to vitest"
# run Claude Code; let it commit as it works
$ patcharc decision "kept the old helpers; agent proposal rejected"
$ patcharc risk "snapshot tests regenerated, not reviewed line by line"
$ patcharc stop
$ patcharc share --visibility public
ArcLink: https://patcharc.dev/a/X9kQ2mN4vR7sWhat the reader gets: the goal, what changed, affected scopes, the phases, and your decisions and risks, plus every commit's patch, all verifiable offline with patcharc verify. What they do not get: the prompts. In 0.2.0 the ArcLink page is minimal and the full review is inside the capsule; attach the .parc to the PR as well if the reader has the CLI.
Which to use
| You want to share | Use |
|---|---|
| A quick look at the session with teammates on Claude | Claude Code share link |
| The raw text in an issue | /export |
| A readable HTML page you host | claude-code-transcripts |
| Continuity into the next agent session | Lore (fork prompt) or Entire (checkpoints) |
| A record a reviewer can verify, without exposing prompts | PatchArc capsule and ArcLink |
Does sharing expose secrets?
Transcripts contain whatever the agent saw: file contents, environment output, pasted tokens. Share links, /export, and HTML transcripts expose all of it. Entire states it redacts secrets before storage. PatchArc shares commit patches rather than the conversation, which is a smaller surface, but its redaction engine is not applied automatically in 0.2.0, so read the capsule (patcharc inspect, unzip -p) before making a link public. In every case, keep secrets out of the session in the first place.
Frequently asked questions
How can I share my Claude Code session with others?
Use the built-in share link for a read-only view, /export for text, a transcript tool for HTML, Lore or Entire for products built around sharing, or PatchArc to share a verified review instead of the transcript.
How do I export a session from Claude Code?
Run /export inside the session. Local JSONL transcripts also live under ~/.claude/projects/ for 30 days by default.
How do I share a conversation from Claude Code without the prompts?
Record the session as a PatchArc Arc and share the capsule or ArcLink. The reader gets commits, decisions, and risks, not the conversation.
Can I share Claude Code projects?
Share links cover a session, not a project. For project-level handoff, combine a session link with the repository and a PatchArc review for each change.
Is there a way to prove the shared record was not edited?
A PatchArc capsule is Ed25519-signed and verifiable offline; the cloud re-verifies it before publishing a link. Transcript exports and share links carry no such check.