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

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

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

Who it is forA 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 problemInviting someone into a live session can let their requests change files or run commands on the host's machine without a check.

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

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

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.

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