An async Magic Wormhole alternative for machines on different schedules
Magic Wormhole and Relay solve different handoff needs. Magic Wormhole connects two peers using a short code and encrypts their traffic end to end. Relay stores a published Bundle so a receiving machine can collect it later. Choose according to timing, access and confidentiality, rather than assuming the tools are interchangeable.
A live transfer between two peers
The standard Magic Wormhole CLI uses send and receive commands to establish a connection between peers. It can carry files and directories directly or through an encrypted transit relay. That is a useful model when you want a code-mediated transfer and both ends can participate in the session.
A stored handoff for an offline receiving machine
With Relay, upload while the sending machine is connected and wait for publication to succeed. You can then end that work session. Later, sign in from your other machine and pull the Bundle from its workspace. You do not need to coordinate a simultaneous sender and receiver session.
Carry the instructions for the next step
A build directory alone may not explain which command to run or which result to review. Relay requires a handoff note alongside the files and keeps workspace history. Use the note for inputs, environment details and the next action. The CLI and compatible agent Skills can work with the same handoff model.
Stored convenience changes the trust model
Relay’s service-side storage is not end-to-end encrypted. It should not be presented as providing Magic Wormhole’s confidentiality model. Review what the service can access, how workspace permissions work, and how deletion is handled before sending sensitive files. For large files, also check capacity and keep your local copy until the transfer completes.
Read the other tool’s official documentation
Relay is an independent project. Product names belong to their respective owners. Check each service’s current documentation before choosing.