# How to share Claude Code sessions with your team

> Five ways to let a teammate read, join or continue a Claude Code session, and what each one gives up.

By Eimen, founder of Leverage Computer. Last reviewed 12 November 2026.

Disclosure: We make Leverage Computer, one of the tools on this page. We describe every product, ours included, from its own public pages, and each fact links to its source. Prices change: check the linked page before you buy. Found something wrong or out of date? Email [founders@leverage.computer](mailto:founders@leverage.computer) and we will fix it.

## The short answer

- **To show a teammate what happened:** share a cloud session link from claude.ai/code. On Team and Enterprise, set it to Team visibility [1].
- **For a session that ran in your terminal:** `/export` saves it as plain text [2]. Lore turns it into a link with transcript, summary and files touched [4].
- **To work in the same live session:** claude-share lets a teammate join from their own Claude Code, with prompts running on your machine [6].
- **If your team works in each other's Claude Code sessions every day:** Leverage Computer. Sessions are shared live in team threads, and anyone can pick one up later on the same machine and files [8][9].

**Figure: Three things "sharing a session" can mean.** Claude Code's own links and `/export` give you a snapshot [1][2]. claude-share adds live pairing [6]. Continuing later needs a computer that keeps the session's files [9].

- A snapshot: A link or an export. The reader sees what happened, frozen at that moment [1][2].
- A live session: Two people in one session. Both see each turn as it happens, and either can type [6][8].
- A hand-off: Someone continues the work later, on the same machine and files [9].

## What "sharing a session" can mean

1. **Read it.** A teammate sees the prompts, replies and changes after the fact.
2. **Join it live.** A teammate watches it happen and can type into it.
3. **Continue it.** A teammate picks up the work later, with the same files and context.
4. **Keep it safe.** Sessions can contain code and secrets, so check who can open the link.

## Side by side

|  | Read | Join live | Continue | Where it runs | Cost |
| --- | --- | --- | --- | --- | --- |
| Cloud session link | Yes [1] | No: the view "doesn't update in real time" [1] | In the cloud; `--teleport` copies it to your terminal [1] | Anthropic-managed VM [1][7] | Included with your Claude plan [1] |
| `/export` | As plain text [2] | No | Paste it into a new session | Your machine | Free |
| Lore | Transcript, summary, decisions, files touched [4] | No | Fork into a new agent session [4] | Your machine | Free and Team ($20 per seat a month) plans [5] |
| claude-share | Yes [6] | Yes [6] | While the host is online | The host's machine [6] | Free, MIT [6] |
| Leverage Computer | Yes [8] | Yes: watch, steer, queue or stop [8] | Yes, on the same VM and files [9] | Its own VM per session [9] | $0.50 per agent hour [10] |

## The options

### Claude Code cloud session links: the built-in option

**Strengths**

- Toggle a cloud session's visibility and share the link [1].
- On Team and Enterprise, Team visibility shows the session to members of your organization, and repository access is checked against the recipient's GitHub account by default [1].
- Sessions started from Claude in Slack are shared with Team visibility automatically [1].

**Weaknesses**

- Recipients "see the latest state when they open the link, but their view doesn't update in real time" [1].
- Only cloud sessions can be shared this way, not sessions in your terminal [1].
- `claude --teleport` gives you a copy: new work there "doesn't appear in the cloud session" [1].
- Anthropic warns that sessions "may contain code and credentials from private GitHub repositories" [1].

**Price.** Included with plans that have cloud sessions [1].

### /export in Claude Code: the quick way for a local session

**Strengths**

- `/export` saves the current conversation as plain text, to a file or the clipboard [2].

**Weaknesses**

- Text only. The teammate gets no files, tools or running state.
- `/share` is not a team-sharing command: it is an alias of `/bug` and sends the conversation to Anthropic [2].
- A feature request for native session sharing was closed as a duplicate of an older request [3].

**Price.** Free.

### Lore: for readable links to past sessions

**Strengths**

- Turns "Claude Code, Cowork, and Codex sessions into a shareable link", run from a Claude Code plugin with `/lore:share` [4].
- Links can be private, workspace or public, and teammates can fork a thread into a new agent session [4].

**Weaknesses**

- A link shows a finished record. Nobody can join the session live.
- Its pricing page describes plans in terms of skills and does not say whether sharing is limited on Free [5].

**Price.** Free $0; Team $20 per seat a month; Enterprise custom [5].

### claude-share: for pairing live on one session

**Strengths**

- "Share a Claude Code session with a link, and a teammate joins it from their own Claude Code" [6].
- By default each edit, command or network call from a guest asks the host first [6].
- MIT-licensed, with a self-hostable room server [6].

**Weaknesses**

- The guest's prompts run on the host's machine, so the session ends when the host does [6].
- Traffic is "encrypted in transit, not end to end" [6].
- Both people need Claude Code 2.1.286 or later [6].

**Price.** Free and open source (MIT) [6].

### Leverage Computer: for teams that work in each other's sessions every day

We make Leverage Computer. This section uses our own public pages, and it says where Leverage Computer does not fit.

In Leverage Computer, every agent session runs on its own VM in a shared workspace, where teammates can open it [8][9].

**Strengths**

- **Live and multiplayer.** Watch a teammate's session live, steer it, queue a message or stop it [8].
- **Shared like a doc.** Keep a session private, share it with a space or the workspace, or invite people as viewers or collaborators [8].
- **Continue later.** Archive a session and reopen it later with the same machine and files [9].
- **Bring local work in.** The CLI imports local Claude Code and Codex sessions [11].
- **Share what it built.** Open what the agent builds through a private preview link [9], or publish a page with versions [8].
- **Session view.** In the app, a session shows the conversation, its files and a terminal side by side [9].

**Where Leverage Computer is the wrong choice**

- **You only need to show someone a transcript now and then.** A cloud session link or `/export` is free and enough.
- **Your code must stay on your own machines.** Leverage Computer does not offer a self-hosted version; claude-share keeps work on the host's machine.
- **You don't want another tool.** Leverage Computer is a workspace your team works in, not a plugin for Claude Code.

**Price.** $0.50 per agent hour on a Standard machine; people are free; use your own Claude plan or credits [10].

## How to choose

1. **Occasional hand-offs?** Use a cloud session link, or `/export` for local work [1][2].
2. **A searchable record of sessions for the team?** Lore [4].
3. **Pair on one session right now?** claude-share [6].
4. **Several people in each other's sessions every day, with work that keeps running?** Leverage Computer [8][9].

## Questions

**Does Claude Code have a share command?**
Not for teammates. `/export` saves the conversation as text, and `/share` is an alias of `/bug`, which sends the conversation to Anthropic [2]. Cloud sessions on claude.ai/code can be shared by link [1].

**Can a teammate continue my Claude Code session?**
With a cloud session link they see its latest state [1]. To keep working on the same files and machine together, you need a shared environment such as Leverage Computer [8][9].

**Is it safe to share a Claude Code session?**
Treat it like sharing code. Anthropic warns that sessions may contain code and credentials from private repositories [1].

## Sources

Checked on 12 November 2026.

1. Claude Code docs, cloud sessions: https://code.claude.com/docs/en/claude-code-on-the-web
2. Claude Code docs, commands: https://code.claude.com/docs/en/commands
3. GitHub, anthropics/claude-code issue 40981: https://github.com/anthropics/claude-code/issues/40981
4. Lore, share: https://lore.link/share
5. Lore, pricing: https://lore.link/pricing
6. claude-share, README: https://github.com/Paradigm-Study/claude-share
7. Claude Code docs, cloud environments: https://code.claude.com/docs/en/cloud-environments
8. Leverage Computer, work in the open: https://leverage.computer/teams/
9. Leverage Computer, the computer underneath: https://leverage.computer/compute/
10. Leverage Computer, pricing: https://leverage.computer/pricing/
11. Leverage Computer, harnesses: https://leverage.computer/harnesses/

[Get started](https://app.leverage.computer/login?mode=signup&utm_source=leverage.computer&utm_medium=markdown&utm_content=/compare/share-claude-code-sessions/)

## More

- [How to share Codex sessions with your team](https://leverage.computer/compare/share-codex-sessions/)
- [How to run Claude Code for a whole team: your options compared](https://leverage.computer/compare/claude-code-for-teams/)
- [Ways to run Claude Code in the cloud, so it keeps working when your laptop is closed](https://leverage.computer/compare/run-claude-code-in-the-cloud/)
- [Work in the open: shared sessions](https://leverage.computer/teams/)
- [Every harness, one workspace](https://leverage.computer/harnesses/)
- [Pricing](https://leverage.computer/pricing/)
- [All comparisons](https://leverage.computer/compare/)