DEDUPED Hot AI repos, turned into use cases Get 5 a day

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

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

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

The problemExplaining a Claude session to a teammate by screenshots or copied text loses context and slows down joint debugging.

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

What you need first

  • Claude Code 2.1.286 or newer, installed by both the host and each guest
  • Your normal Claude authentication
  • Git and Node 20+ if you use the setup script or self-host a server
  • A Cloudflare account and browser authorization only if you deploy your own Worker

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 for your agent

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.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page