How to share Claude Code sessions with your team

• To show a teammate what happened: share a cloud session link from claude.ai/code. On Team and Enterprise, set it to Team visibility¹.
• For a session that ran in your terminal: /export saves it as plain text². Lore turns it into a link with transcript, summary and files touched⁴.
• To work in the same live session: claude-share lets a teammate join from their own Claude Code, with prompts running on your machine⁶.
• 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}.

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.

Claude Code cloud session links: the built-in option

Strengths

• Toggle a cloud session's visibility and share the link¹.
• 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¹.
• Sessions started from Claude in Slack are shared with Team visibility automatically¹.

Weaknesses

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

Price. Included with plans that have cloud sessions¹.

/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².

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².
• A feature request for native session sharing was closed as a duplicate of an older request³.

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⁴.
• Links can be private, workspace or public, and teammates can fork a thread into a new agent session⁴.

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⁵.

Price. Free $0; Team $20 per seat a month; Enterprise custom⁵.

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"⁶.
• By default each edit, command or network call from a guest asks the host first⁶.
• MIT-licensed, with a self-hostable room server⁶.

Weaknesses

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

Price. Free and open source (MIT)⁶.

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⁸.
• Shared like a doc. Keep a session private, share it with a space or the workspace, or invite people as viewers or collaborators⁸.
• Continue later. Archive a session and reopen it later with the same machine and files⁹.
• Bring local work in. The CLI imports local Claude Code and Codex sessions¹¹.
• Share what it built. Open what the agent builds through a private preview link⁹, or publish a page with versions⁸.
• Session view. In the app, a session shows the conversation, its files and a terminal side by side⁹.

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¹⁰.

Inside one Leverage Computer session

People

Watch it live

Steer or queue a message

Approve tool calls

Share as viewer or collaborator

Environment

Variables per space or session

Secrets added at the network

Values hidden from transcripts

The computer

Its own VM with sudo

Claude Code, Codex or Grok Build

Sleeps when idle

terminalbrowserfilesdisk

Git

Every turn committed

Team memory and skills

What it makes

Pull requests with Auto-fix

Private preview links

Published pages

Scheduled and event runs

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⁴.
3. Pair on one session right now? claude-share⁶.
4. Several people in each other's sessions every day, with work that keeps running? Leverage Computer^{8, 9}.

• How to share Codex sessions with your team
• How to run Claude Code for a whole team: your options compared
• Ways to run Claude Code in the cloud, so it keeps working when your laptop is closed
• Work in the open: shared sessions
• Every harness, one workspace
• Pricing
• All comparisons