# AI use cases for Claude Share (Paradigm-Study/claude-share)

Repo: [Paradigm-Study/claude-share](https://github.com/Paradigm-Study/claude-share) | Use cases: 4 | Page: https://dedupedai.com/use-cases/paradigm-study-claude-share/

Shared Sessions is a Claude Code plugin that lets a host share a live session link so teammates can join, see the same prompts, replies and tool results, and work together.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Pair with a teammate on a live Claude Code task: https://dedupedai.com/use-cases/paradigm-study-claude-share/pair-on-live-claude-task/
- Review Claude's replies and tool results together: https://dedupedai.com/use-cases/paradigm-study-claude-share/review-claude-work-together/
- Let guests watch or ask before edits and commands: https://dedupedai.com/use-cases/paradigm-study-claude-share/control-guest-permissions/
- Host your own Shared Sessions room server: https://dedupedai.com/use-cases/paradigm-study-claude-share/host-private-room-server/

## How to pair with a teammate on a live Claude Code task with Claude Share

Repo: [Paradigm-Study/claude-share](https://github.com/Paradigm-Study/claude-share) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Share a session link so a teammate joins with shared history and both investigate the same code.

**Who it is for:** A developer who is stuck on a bug or codebase question and wants a teammate to join the same Claude session right away.

**The problem:** Explaining a Claude session to a teammate by screenshots or copied text loses context and slows down joint debugging.

**The outcome:** The teammate is in the host's session with its shared history, and both people see the same prompts, streamed replies and tool results.

### Steps

1. In a terminal, run `claude plugin marketplace add Paradigm-Study/claude-share`
2. Run `claude plugin install shared-session@claude-share`, then start a new session.
3. Host: press Share above the prompt or type `/share-session`, then copy the link.
4. Teammate: paste the link into a fresh Claude Code session and send it.
5. Either person: ask Claude to read the project README and confirm both sessions show the same reply.

### Prompt to paste into your agent

```text
In the Paradigm-Study/claude-share repo, install the shared-session plugin and start a host session that shares a link for the project at <project-path>. Output the share link and confirm the guest session at <guest-session> shows the same prompt and reply. Verify that the guest's prompt ran on the host and the guest's model was not called.
```

### Caveat

Sharing passes the transcript and shared files through the public room server, which is not end to end encrypted, so do not share sessions with secrets.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/paradigm-study-claude-share/pair-on-live-claude-task/

## How to review Claude's replies and tool results together with Claude Share

Repo: [Paradigm-Study/claude-share](https://github.com/Paradigm-Study/claude-share) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Walk a teammate through Claude's replies, tool cards, files and previews inside their own session.

**Who it is for:** A reviewer or lead who needs to check what Claude did in a session without rerunning the work.

**The problem:** Reviewing another person's Claude session means asking for a summary, since the tool results and changed files are hard to reconstruct.

**The outcome:** The reviewer sees the host's replies, tool cards, files and supported previews in their own session, and can react to replies or @name teammates in the transcript.

### Steps

1. Host: share the session with `/share-session` and send the link to the reviewer.
2. Reviewer: join by pasting the link into a fresh Claude Code session.
3. Either person: type `/room` to see the people, the timeline of turns and the files Claude changed.
4. Either person: react to Claude's replies in the transcript or use `@name` to point at a teammate.
5. Host: type `/stop-sharing` when the review is done, which ends the room for everyone.

### Prompt to paste into your agent

```text
Using the Paradigm-Study/claude-share plugin, share the current session on the project at <project-path> and open /room to list the files Claude changed. Output that file list and the timeline of turns. Verify that the reviewer session at <reviewer-session> shows the same tool results.
```

### Caveat

Guests see only the first 40 lines of each tool result and subagent inner steps are not mirrored, so a review may miss details.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/paradigm-study-claude-share/review-claude-work-together/

## How to let guests watch or ask before edits and commands with Claude Share

Repo: [Paradigm-Study/claude-share](https://github.com/Paradigm-Study/claude-share) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Keep the host in control with approval rules or a watch-only guest mode for shared sessions.

**Who it is for:** A host who wants a teammate or outside reviewer in the session but must keep control of edits, commands and network use on their machine.

**The problem:** Inviting someone into a live session can let their requests change files or run commands on the host's machine without a check.

**The outcome:** Guest requests to edit, run commands or use the network ask the host first, or the guest is limited to watch-only mode.

### Steps

1. Host: start the session in the project folder and type `/share-session`.
2. Host: keep the default rule, where a guest's request to edit, run commands or use the network asks the host first.
3. Host: for a read-only guest, choose watch-only mode when the room is set up.
4. Host: open `/room` to check the people in the room and the host controls.
5. Host: approve or deny guest requests as they arrive, and type `/stop-sharing` to end the room.

### Prompt to paste into your agent

```text
With the Paradigm-Study/claude-share plugin, open a shared session for the project at <project-path> using the default approval rules. Output the room's permission settings and the list of guests from /room. Verify that a guest request to run a command at <test-command> waits for host approval and does not run on its own.
```

### Caveat

The README does not give the exact command or menu for choosing watch-only mode, so check the full guide before relying on it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/paradigm-study-claude-share/control-guest-permissions/

## How to host your own Shared Sessions room server with Claude Share

Repo: [Paradigm-Study/claude-share](https://github.com/Paradigm-Study/claude-share) | Difficulty: Advanced | Time: 60 minutes | Basis: From the README

Deploy a Cloudflare Worker or Node server so your team keeps rooms on its own infrastructure.

**Who it is for:** A platform or DevOps engineer at a team that cannot send session transcripts through the public default server.

**The problem:** The public default server receives the shared transcript, tool results, side chat and shared files, which some teams cannot accept.

**The outcome:** Your team runs its own room server, and sharing by link goes through that server instead of the public one.

### Steps

1. Run `git clone https://github.com/Paradigm-Study/claude-share.git` and `cd claude-share`.
2. Run `node scripts/setup.mjs deploy` from the clone with Node 20+ installed.
3. Complete the Cloudflare account setup and browser authorization when prompted.
4. For an existing server, run `node scripts/setup.mjs host --server https://your-server`.
5. Run `node scripts/setup.mjs check --live` to test sharing, resuming, stopping and joining through the selected server. (inferred, check the README)

### Prompt to paste into your agent

```text
In the Paradigm-Study/claude-share repo, run the setup script to deploy a room server to <cloudflare-account> and point the plugin at it. Output the server URL and the result of the check command. Verify that a temporary session shares and joins through that URL without touching the public default server.
```

### Caveat

Cloudflare account setup and browser authorization need a person, so an agent can only automate the steps after that.

Risk, credentials: Deployment needs your Cloudflare account and browser authorization, so only run it with credentials you control and keep them out of agent prompts and logs.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/paradigm-study-claude-share/host-private-room-server/
