Async file transfer when your other machine is offline
An asynchronous file transfer separates sending from receiving. Upload once to a service that stores the files, then download from the receiving machine when it reconnects. This is useful when a workstation finishes a job before your laptop, remote computer, or next work session is available.
1. Send files with the context to continue
Use the Relay CLI to push a file or directory as a Bundle. Add the required handoff note: what the output contains, where it came from, and what to do next. The sender must stay connected until upload and publication finish. A successful push gives you a Bundle to collect later.
2. Receive on your own schedule
Sign in on the receiving machine, open the correct workspace, and pull the published Bundle. Files and notes stay associated, while workspace history helps identify the handoff. Relay transfers selected Bundles; it does not continuously mirror every change in a local folder.
3. Plan for large files and interrupted connections
Check available storage before sending a large dataset or build output. The CLI supports interrupted transfer recovery; keep the original files and transfer state so it can continue. Recovery does not remove the need for bandwidth or a reachable service. Review the transfer result before deleting your local copy.
Choose stored handoffs with the right privacy expectations
Stored transfers fit machines that are online at different times. Relay uses service-side storage and account access; it is not end-to-end encrypted. Read the trust page before sending sensitive data. For a live encrypted peer transfer, consider whether a tool such as Magic Wormhole better fits the job.