Shared Sessions for Claude Code plugin
A Claude Code plugin: share a session link and a teammate sees the same prompts, replies and tool results in their own Claude Code
- 734 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- A guest can edit files, run commands and use the network through your machine if you approve the request
- The session transcript and shared files pass through the room server without end-to-end encryption
- Moving to the cloud sends your Claude token and project files to a server container
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/shared-sessions-for-claude-codeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- A guest can edit files, run commands and use the network through your machine if you approve the request
- The session transcript and shared files pass through the room server without end-to-end encryption
- Moving to the cloud sends your Claude token and project files to a server container
This is third-party code. Review the repository files before installing.
What it does
The host presses Share above the prompt or types /share-session and sends a teammate the link. The teammate pastes it into a fresh Claude Code session, and both see the prompts, streamed replies and tool results. The host's machine does the work. Guest prompts run on the host in turn, and the guest's own model is not called. By default any guest request to edit a file, run a command or use the network asks the host first. A watch-only mode exists. The /room command shows people, the timeline of turns, the files Claude changed, side chat and host controls, and /who lists who is present. You can react to Claude's replies and mention a teammate with @name. With /share-preview <port> the host opens a local dev server to guests. The session can move to a container on the room server and come back. The /team command turns on optional teams with sign-in, a live session list and invitations.
Who it is for. For teams who work through a task in one Claude Code session: pair programming, review and helping a teammate remotely.
Good fit when
- A teammate is stuck on a bug and you want to show them the session and ask Claude to look at the same code together
- You need a review of the result: the guest sees the host's replies, tool cards, files and page previews
- The host builds a frontend and opens the local dev server to guests with /share-preview 3000
- The session has to keep going while the host sleeps or travels: moving the host to the cloud helps
- You want watch-only mode where the guest only observes and runs nothing on your machine
Not a fit when
- The session holds secrets or private code that must not pass through a shared room server
- You need two independent sessions working in parallel: here everyone shares one session and guest prompts run in turn
- Someone on the team cannot update Claude Code to the version the plugin requires
- You only need shared access to project files without running an agent: plain git does that
Example request
Read the project README and explain to both of us how the build runs: my teammate just joined by the link.Limitations
You need Claude Code 2.1.286 or newer on both sides. Check with `claude --version` and update with `claude update`. Previews need Node 20+, POSIX sh and the host's live curl stream.
The public room server is run by the project. It receives the shared transcript, tool results, side chat, reactions and shared files. Traffic is encrypted in transit only, with no end-to-end encryption. Anyone with a room link can join unless access is restricted to a team. Rooms and files are deleted 24 hours after sharing stops. The public service allows 20 people, 100 MB of files and 128 open previews per room.
Moving to the cloud sends the project files, the conversation and the host's Claude token to a container the server starts. The token comes from `claude setup-token` and the server keeps only a hash of it. You can host your own server on a Cloudflare Worker or on Node.
How to disable. The host types /stop-sharing and the room ends for everyone. To remove the plugin, uninstall shared-session from the /plugin menu in Claude Code. If you deployed your own server, stop it and delete the Worker in Cloudflare.
FAQ
How do I install Shared Sessions in Claude Code?
Both people need the plugin: `claude plugin marketplace add Paradigm-Study/claude-share`, then `claude plugin install shared-session@claude-share`. Leave the server setting empty. A new session picks up the plugin, and Claude Desktop must be quit and reopened.
Whose model answers the guest's prompts?
The host's model. Guest prompts run on the host's machine in turn and the guest's own model is not called. The host therefore decides token spend and access rights.
How does a guest open the host's local dev server?
The host types /share-preview and a port number, for example 3000. The guest presses Open preview and the page opens at the host's own address, so OAuth callbacks and 127.0.0.1 backends work. If those ports are free on the guest's machine the page opens in Claude Desktop's browser or the guest's own browser, and if they are taken it opens in a separate window.
What does moving the session to the cloud do?
Move to cloud in the room settings hands the host to a Claude Code container on the room server, so teammates keep working while your computer sleeps. Every call a teammate's prompt makes asks you first. Bring home returns the session with the changes to your files.
Can I host my own room server?
Yes. From a clone of the repository run node scripts/setup.mjs deploy (Node 20+ required). The server runs on a Cloudflare Worker or on Node. A person completes the Cloudflare account setup and browser authorization. For an existing server there is node scripts/setup.mjs host --server https://your-server.
Discussion
No questions or reviews yet.
Related
PluginsA set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
A debugging tool for Claude Code that reads the session logs already saved on disk and shows exact file paths, diffs, model thinking and a category-by-category
Nick Tune's plugin marketplace for Claude Code: checks before a task is handed in, code review and TDD personas
A set of Claude Code mods: status lines above the prompt, a guard against risky commands and a few small games
A set of slash commands, skills and subagents for Claude Code: review, tests, security, releases, docs and GitHub to Linear sync
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Shared Sessions for Claude Code (this entry) | no | 734 | |
| Claude Squad | no | 8,694 | runs several of your own sessions in parallel on one computer and lets no teammate into them |
| Octogent | no | 1,415 | a dashboard for one person's many Claude Code sessions, with no shared access for a teammate |
README in short
An 8-second demo of an invitation arriving in Claude Desktop comes first, then installation and a trial run on a scratch project. A separate section explains in detail what the public server sees and how long it keeps it, and the last part covers self-hosting and troubleshooting.