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

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

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

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

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

The outcomeThe 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.

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

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.

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