Shared Sessions for Claude Code

Share a Claude Code session with a link. Teammates open it, land in a Claude Code session of their own that is attached to yours, and talk to it. Everyone sees every prompt and every reply, live, as normal transcript rows.

• One machine does the work. The session that shared is the host. Every turn and every tool runs there, in its folder, under its login.

• Everyone else is a guest. A guest's prompt goes to the host and runs in turn. Every host turn plays out in each guest's own transcript as a prompt and a streamed reply. A guest's own model is never called.

• The host stays in charge. When a guest's prompt makes Claude write a file, run a command or reach the network, the host is asked first, whatever the host's permission mode. The question shows the exact command or diff. The host can also make the session watch-only.

• It lives in Claude's own UI. In Claude Desktop and the terminal:

  • a teammate's prompts carry their dot avatar and name;
  • the footer and working line say who's here and whose turn it is;
  • a Room panel has the session on top (Live, who's here, the link), then its pages: People, Chat (a side chat Claude never reads, with who came and went), Shown (what Claude showed) and Settings;
  • everyone has a color of their own, the same on their face, their name in the Room and the chat, and their prompts in your transcript;
  • in Desktop, the session list marks and pins shared sessions.

• What Claude shows, everyone sees. When the host's Claude opens a file in the side panel or the Files pane, draws a widget, or opens a page or a local dev server in the browser pane, each guest's own Claude Code opens the same thing. A dev server it only gives the address of (http://localhost:3000/…) is shared too, at that page, once something answers there; so are the ones it opened or gave out before you pressed Share everything, if they're still running. Files are saved in the guest's project under .shared-session/ (kept out of git). A dev server opens through its preview link unless the host explicitly allows forwarding; then each guest presses Open in the Room to use their own http://localhost:<local-port>, TCP-forwarded through the room server. The host's port is preferred; if busy, an available local port is used instead. Screenshots the host's Claude takes (the browser pane's, a computer's) and images it opens show in the guest's tool cards as they do in the host's. A page it publishes (an Artifact) arrives with its pictures and other files beside it, and opens whole in the guest's browser pane, again whenever it's opened again; nobody needs the private claude.ai link. The Room shows anyone whose plugin is out of date, and a guest who types the update command into the session has it run on their own computer. A guest's message can carry attachments (images, PDFs): they're saved in the host's project and the host's Claude opens them.

• Teams. Sign in with GitHub or Google, make a team, and what you share goes to it: everyone in the team sees your live sessions in their Team panel and joins with one press (Join all for every one). Teammates come in by invite link, by their email's domain or by their GitHub organization; each team says whether its sessions are for its people only or for anyone with the link.