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 who needs to hand a teammate's agent a concrete file, such as a schema or config, rather than describing it in words.
The problemPasting file contents into chat is error-prone, and agents on different machines cannot read each other's folders.
The outcomeThe recipient's engine saves a copy of the file under ~/.reason/network/inbox and the message says where it is.
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 find the teammate session you want to reach. - Run
reason-network send alice/api-claude --file schema.json "the schema I meant"from the folder that holds the file. - Tell the recipient to look in ~/.reason/network/inbox, where the saved copy and the path in the message point.
- Keep the file within limits: up to 10 text files, 256 KB each, and 512 KB in total, and never a hidden file.
Prompt for your agent
In the reason-machines/reason-network repo, send the text file <path> to <teammate>/<session> with `reason-network send <teammate>/<session> --file <path> "<note>"`. 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.
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