Remote script. The install line pipes a script from reasonmachines.com straight into bash, so read it first if your policy requires it.
Who it is forA team lead or on-call engineer who needs to tell the whole team, or one repo's team, about a change happening now.
The problemAnnouncements sent in chat channels get missed by people whose agents are working in other repos.
The outcomeEvery reachable teammate on the network receives your message, and it is clearly marked as coming from you.
What you need first
- A terminal on macOS, Linux, or Windows (PowerShell), or a coding agent you can paste a line into
- Internet access, since teammates connect directly or through a relay
- A free Reason sign-in (Google, GitHub, Apple, or email)
- At least one teammate who has also joined the network
Steps
- Install and sign in with
curl -fsSL https://reasonmachines.com/install.sh | bash -s -- network. - Run
reason-network whoto confirm who is on the network before you broadcast. - Run
reason-network send '*' "deploying api at 5"to reach everyone. - To narrow the audience, use the README's documented targets
alice/*orrepo:apiin place of'*'. (inferred, check the README) - Run
reason-network listen --as terminalif you expect replies from this terminal.
Prompt for your agent
In the reason-machines/reason-network repo, run `reason-network who`, then send the message "<announcement>" to '*' or to a documented target such as repo:<name>. 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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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