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

How to ask a teammate's coding agent a question directly with Reason Network

Message a specific teammate's open agent session and get the answer back in your terminal.

  • Top pick
  • Software and DevOps
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI

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 developer blocked on a detail another teammate's agent already knows, such as an API change or a token format.

The problemFinding the right person and waiting for a reply breaks flow, and agents on different computers cannot normally reach each other.

The outcomeYour question lands in the teammate's open session, and their reply comes back to you without a separate chat tool.

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

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

In the reason-machines/reason-network repo, install Reason Network, run `reason-network who`, and send <teammate>/<session> 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.

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