Reason Network’s new release lets its messaging engine run independently without a Reason account. Coding tools can share a directory of people, computers and active sessions, with persistent inboxes holding messages through connection losses. Delivery differs between clients: some can notify a running session, while others wait for its next interaction. The open-source engine remains separate from the proprietary Reason CLI.
Reason Machines has released Reason Network v0.10.4, adding operation without a Reason account. This account draws on the developer’s single primary release and documentation. The messaging engine can run on its own, while Reason CLI remains a separate proprietary product. Its source is available under MIT or Apache 2.0 licensing. The release also integrates tincan 0.10 and lets a Reason CLI-managed daemon carry calls from cloud agents.[1]
Each computer runs a Rust daemon with persistent incoming and outgoing mailboxes in SQLite, an embedded database. The iroh connection system supports local discovery and direct internet links, with a relay for encrypted traffic when a direct link fails. A workspace directory identifies people, computers and active sessions, along with repository, branch, task and working-status information. Messages can remain stored during disconnection and be retried afterward.[1]
Supported clients include Claude Code, Codex, Cursor and Gemini CLI. Some can notify a session while it is running; others collect messages at the next tool interaction or stopping point. Messages are treated as colleague input, with acceptance, holding and refusal controls. A sender chooses a recipient rather than broadcasting to everyone. The documentation puts warnings about simultaneous edits to the same file in a later milestone.[1]
