# AI use cases for Reason Network (reason-machines/reason-network) Repo: [reason-machines/reason-network](https://github.com/reason-machines/reason-network) | Use cases: 4 | Page: https://dedupedai.com/use-cases/reason-machines-reason-network/ Reason Network is a peer-to-peer daemon that lets your team's coding agent sessions see each other and exchange messages and small text files. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Ask a teammate's coding agent a question directly: https://dedupedai.com/use-cases/reason-machines-reason-network/ask-teammate-agent-question/ - Approve a teammate's request through a pop-up: https://dedupedai.com/use-cases/reason-machines-reason-network/approve-teammate-request-from-popup/ - Send a small text file to a teammate's agent: https://dedupedai.com/use-cases/reason-machines-reason-network/share-small-text-file-with-teammate-agent/ - Announce a deploy to the whole team from your terminal: https://dedupedai.com/use-cases/reason-machines-reason-network/announce-deploy-to-whole-team/ ## How to ask a teammate's coding agent a question directly with Reason Network Repo: [reason-machines/reason-network](https://github.com/reason-machines/reason-network) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Message a specific teammate's open agent session and get the answer back in your terminal. **Who it is for:** A developer blocked on a detail another teammate's agent already knows, such as an API change or a token format. **The problem:** Finding the right person and waiting for a reply breaks flow, and agents on different computers cannot normally reach each other. **The outcome:** Your question lands in the teammate's open session, and their reply comes back to you without a separate chat tool. ### Steps 1. Run `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network` in a terminal, or paste the join line from https://reasonmachines.com/network to your coding agent. 2. Sign in with Reason in the browser that opens; the coding agents on this computer are set up. 3. Run `reason-network who` to see teammates' sessions with their repo, branch, and busy or idle state. 4. Run `reason-network send alice/api-claude "did the token format change?"` to message one session. 5. Run `reason-network listen --as terminal` to receive replies to what you sent from this terminal. ### Prompt to paste into your agent ```text In the reason-machines/reason-network repo, install Reason Network, run `reason-network who`, and send / the question "did the token format change?". Expected output: the session list followed by the teammate's reply after running `reason-network listen --as terminal`. Verify that the target session appears as idle or busy in the `who` output before sending. ``` ### Caveat Delivery timing differs by agent: Claude Code, Codex, opencode, pi, and Reason get messages mid-session, while Cursor, Gemini, Copilot, and Grok see them at their next step. Risk, remote script: The install line pipes a script from reasonmachines.com straight into bash, so read it first if your policy requires 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/reason-machines-reason-network/ask-teammate-agent-question/ ## How to approve a teammate's request through a pop-up with Reason Network Repo: [reason-machines/reason-network](https://github.com/reason-machines/reason-network) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Let your agent ask you Approve or Deny for a teammate's request while you are away from it. **Who it is for:** A team member who has to sign off on a deploy or similar action that a teammate's agent requests, but is not at the keyboard for that session. **The problem:** A teammate's agent can be stuck waiting on a decision that only you can make, and you may not be watching your coding session. **The outcome:** You see a pop-up with Approve or Deny and an optional note, and your answer returns to your agent as coming from you. ### Steps 1. Install and sign in with `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network`, then confirm your agents with `reason-network setup`. 2. On macOS, allow notifications from Script Editor in System Settings so pop-ups can appear. 3. Ask a teammate to test the flow by running `reason-network send / --notify "approve the deploy?"`. (inferred, check the README) 4. When the pop-up appears, choose Approve or Deny and add a note if needed. 5. Confirm that your agent received the answer as your own sign-off, not as a regular message. ### Prompt to paste into your agent ```text In the reason-machines/reason-network repo, run `reason-network setup` to list configured agents and how their messages are handled, then have a teammate send a test with `--notify`. Expected output: an Approve or Deny pop-up on your screen and the chosen answer delivered back to your agent. Verify that the pop-up appears and that the answer is attributed to you. ``` ### Caveat On macOS the pop-ups come from Script Editor, so they will not show until notifications from that app are allowed in System Settings. Risk, remote script: The install line pipes a script from reasonmachines.com straight into bash, so read it first if your policy requires 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/reason-machines-reason-network/approve-teammate-request-from-popup/ ## How to send a small text file to a teammate's agent with Reason Network Repo: [reason-machines/reason-network](https://github.com/reason-machines/reason-network) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Attach a schema, config, log, or code file to a message for a specific teammate's session. **Who it is for:** A developer who needs to hand a teammate's agent a concrete file, such as a schema or config, rather than describing it in words. **The problem:** Pasting file contents into chat is error-prone, and agents on different machines cannot read each other's folders. **The outcome:** The recipient's engine saves a copy of the file under ~/.reason/network/inbox and the message says where it is. ### Steps 1. Install and sign in with `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network`. 2. Run `reason-network who` to find the teammate session you want to reach. 3. Run `reason-network send alice/api-claude --file schema.json "the schema I meant"` from the folder that holds the file. 4. Tell the recipient to look in ~/.reason/network/inbox, where the saved copy and the path in the message point. 5. Keep the file within limits: up to 10 text files, 256 KB each, and 512 KB in total, and never a hidden file. ### Prompt to paste into your agent ```text In the reason-machines/reason-network repo, send the text file to / with `reason-network send / --file ""`. Expected output: a delivered message that names the saved copy under ~/.reason/network/inbox. Verify that the file is plain text, under 256 KB, and not a hidden file before sending. ``` ### Caveat Only small text files are supported (markdown, code, JSON, logs, config), so binary files and anything over the size limits will not go through. Risk, remote script: The install line pipes a script from reasonmachines.com straight into bash, so read it first if your policy requires 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/reason-machines-reason-network/share-small-text-file-with-teammate-agent/ ## How to announce a deploy to the whole team from your terminal with Reason Network Repo: [reason-machines/reason-network](https://github.com/reason-machines/reason-network) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Send one message to everyone on the network, or to a chosen group, sent from you and not from an agent. **Who it is for:** A team lead or on-call engineer who needs to tell the whole team, or one repo's team, about a change happening now. **The problem:** Announcements sent in chat channels get missed by people whose agents are working in other repos. **The outcome:** Every reachable teammate on the network receives your message, and it is clearly marked as coming from you. ### Steps 1. Install and sign in with `curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network`. 2. Run `reason-network who` to confirm who is on the network before you broadcast. 3. Run `reason-network send '*' "deploying api at 5"` to reach everyone. 4. To narrow the audience, use the README's documented targets `alice/*` or `repo:api` in place of `'*'`. (inferred, check the README) 5. Run `reason-network listen --as terminal` if you expect replies from this terminal. ### Prompt to paste into your agent ```text In the reason-machines/reason-network repo, run `reason-network who`, then send the message "" to '*' or to a documented target such as repo:. Expected output: a confirmation that the message was sent to the chosen audience. Verify that the audience matches who you intended by reviewing the `who` output first. ``` ### Caveat The README documents `'*'`, `alice/*`, and `repo:api` as audience targets, but it does not describe every filter, so check the `who` output before broadcasting. Risk, remote script: The install line pipes a script from reasonmachines.com straight into bash, so read it first if your policy requires 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/reason-machines-reason-network/announce-deploy-to-whole-team/