# How do you share a Claude Code session?

Anthropic's options let a teammate read a session or take a copy. Typing into the same live session takes another tool.

Published 2026-10-05 by Richard Kaminsky and Mitchell Lipyansky, the co-founders of Poly. Canonical: https://usepoly.co/share-claude-code-session
Poly is a multiplayer AI coding workspace: a shared room where your team works with one AI agent, together. Free to start: https://usepoly.co/

**You can share a Claude Code session in three ways, and only the third lets a teammate work in it with you. Claude Code on the web shares a cloud session by link, which the recipient sees as it was when they opened it; `/export` and the session's transcript file hand over a copy someone can read or resume on their own machine; and third-party tools such as MobSession, Happier, Manycode and Lody put your live session where teammates can type. As of October 2026 Claude Code has no built-in way for two people to work in one session, and Anthropic's terms don't allow sharing an account to get one.**

## Key takeaways

- Claude Code on the web shares a cloud session as Team (on Team and Enterprise) or Public (on Pro and Max). The recipient's view doesn't update live.
- `/export` writes a plain-text transcript, and a session's `.jsonl` file under `~/.claude/projects` can be reopened elsewhere with `claude --resume`.
- Remote Control, teleport and cross-session messaging all work inside your own account. Agent Teams is several agents for one person.
- For a live shared session, use a third-party tool, or run the agent somewhere everyone can reach.

*Ways to share a Claude Code session, from each vendor's pages, October 5, 2026.*

| Option | What the other person gets | Can they type? | Updates live? | Cost |
| --- | --- | --- | --- | --- |
| Claude Code on the web link | A cloud session to read | Not in Anthropic's docs | No, latest state on open | Your Claude plan |
| /export | A plain-text transcript | No | No | Free |
| Transcript file and claude --resume | A copy they continue on their machine | In their own copy | No | Free |
| Remote Control | Nothing; it's for your own devices | Only you | Yes, for you | Your Claude plan |
| MobSession | A link to your live session | Prompts, after the host approves | Yes | Free; Team $250 a month |
| Happier | A view-only, can-edit or public link | With can-edit | Yes | Free, open source |
| Manycode (ccshare) | A shared terminal | Yes, unless read-only | Yes | Free, open source |
| A Poly room | One live session in a browser | Yes; any member can approve | Yes | Free start; $20 or $50 per person who runs the AI |

## Can two people use Claude Code at the same time?

Not in one session. Each Claude Code session belongs to one account, and that person types the prompts and answers the permission prompts. Remote Control lets you steer your own session from your phone or the web, and it "grants no one else access" ([Anthropic](https://code.claude.com/docs/en/remote-control)). Agent Teams, an experimental feature that's off by default, has one lead session coordinate several Claude instances, and their permission prompts all come back to the lead for one person to approve ([Anthropic](https://code.claude.com/docs/en/agent-teams)).

Sharing a login isn't the answer either. Anthropic's [Consumer Terms](https://www.anthropic.com/legal/consumer-terms), which cover Free, Pro and Max, say you may not share your login or make your account available to anyone else, and Claude Code's [legal page](https://code.claude.com/docs/en/legal-and-compliance) says Pro and Max limits assume individual use. The request for shared sessions, [#60082](https://github.com/anthropics/claude-code/issues/60082), has been open since May 18, 2026, with 12 comments, 25 thumbs-up and no reply from Anthropic as of October 5.

## How do you share a session with Claude Code on the web?

Cloud sessions in [Claude Code on the web](https://code.claude.com/docs/en/claude-code-on-the-web) have a visibility setting and a link. On Team and Enterprise the choices are Private and Team, which shows the session to members of your organization. On Pro and Max they're Private and Public, which shows it to anyone logged in to claude.ai, and Anthropic warns that a session may contain code and credentials from private repositories.

The recipient sees the latest state when they open the link, and their view doesn't update in real time. Anthropic's docs don't describe recipients sending messages. To carry on with the work, they'd need your account: teleporting a cloud session into a terminal requires being signed in as the person who ran it, and the terminal copy then goes its own way.

## How do you hand off a local session?

- **`/export`** writes the conversation as plain text to a file or the clipboard ([commands](https://code.claude.com/docs/en/commands)). Good for a pull request or a Slack thread.
- **The transcript file.** Claude Code keeps each session as a `.jsonl` file under `~/.claude/projects`, for 30 days by default. A teammate can reopen a copy with `claude --resume` and the file's path, adding `--fork-session` to give it a new ID ([sessions](https://code.claude.com/docs/en/sessions)). The format is internal and changes between versions, and transcripts aren't encrypted: anything the session read, such as a `.env` file, is in there.
- **A shared setup.** A committed `CLAUDE.md`, slash commands and MCP configuration make everyone's separate sessions start from the same place. More in [Claude Code collaboration](/claude-code-collaboration).

## Which tools let a teammate type into your session?

These run Claude Code on your machine, on your plan, and add a way in for others. Check Anthropic's terms first: its legal page bars third-party developers from routing requests through Free, Pro or Max credentials on behalf of their users.

- **[MobSession](https://mobsession.ai)** shares a real Claude Code session on your machine by link. Teammates submit prompts, and each one waits for the host's approval, on rules the host sets. Free; Team $250 a month flat.
- **[Happier](https://happier.dev)** is an open-source client for sessions on your computer. Share a session view-only, as can-edit so a friend types into the same transcript, or as a read-only public link. Free, MIT.
- **[Manycode](https://getccshare.vercel.app)**, formerly ccshare, wraps Claude Code in a shared terminal that friends join with a six-character code. Everyone can type, or the host starts it read-only. Free, MIT.
- **[Lody](https://lody.ai)** is a team workspace where you open a teammate's session and keep chatting, running on your machines with the plan you already pay for. Free for up to three members; Plus $8 a seat a month, billed yearly.
- **Terminal sharing.** tmux can give another user on the same machine read-only or writable access to a session, and VS Code Live Share can share a terminal read/write, which gives guests the same access to your terminal that you have ([Microsoft](https://learn.microsoft.com/en-us/visualstudio/liveshare/use/share-server-visual-studio-code)).

To share a record instead: **[Claudebin](https://claudebin.com)** publishes a session as a read-only, embeddable page (free, MIT); **[Lore](https://lore.link)** turns Claude and Codex sessions into links your team can read (free; Team $20 a seat a month); and the **Session Share** skill exports a session to a file that a teammate imports into agent-deck. More in [Collaborative Claude Code tools](/collaborative-claude-code-tools).

## What about a session that doesn't run on anyone's laptop?

The tools above keep the agent on the host's machine, under the host's account. The other way is to run the agent somewhere the whole team can reach. Poly (usepoly.co) runs Claude Code, and Codex, in a sandbox on its servers, inside a browser room. Everyone sees each turn as it runs and anyone can prompt. In the modes that ask, any member can approve a change before it lands, and every turn ends with a receipt naming who ran it and what it cost. Nobody needs a Claude subscription or an API key, because Poly's plans include the models. Free to start. [What is Poly?](/what-is-poly)

## Which should you use?

- **Show a teammate what happened:** a Claude Code on the web link, or `/export`.
- **Hand the work over:** the transcript file and `claude --resume`, plus a shared setup in git.
- **Pair on one session from your laptop:** MobSession, Happier, Manycode or a shared terminal.
- **A team, including people who don't code, steering one agent with approvals:** a Poly room.

## Common questions

**Can you share a Claude Code session?**

Yes, as a link or a copy. Claude Code on the web shares cloud sessions by link, /export writes a transcript, and a session's .jsonl file can be resumed on another machine. None of these lets a second person type into the same live session; third-party tools such as MobSession and Happier do.

**Can two people use one Claude Code account?**

Not under Anthropic's Consumer Terms, which say you may not share your login or make your account available to anyone else. Team and Enterprise plans give each person their own seat.

**Is there Live Share for Claude Code?**

Not from Anthropic. VS Code Live Share can share a terminal read/write, so a guest can type into a Claude Code CLI running there, with the same access to your terminal that you have. Manycode and Happier do the same for Claude Code specifically.

**Does a shared Claude Code link update live?**

No. Anthropic's docs say recipients see the latest state when they open the link, and their view doesn't update in real time.

More guides: https://usepoly.co/guides · Security: https://usepoly.co/security · Pricing: https://usepoly.co/pricing