Doing this with an agent? Paste this page into Claude Code or Codex as context. Every command is copy-paste and self-contained, so the agent can run the switch end to end.
How the platforms map
Move your state
Orgo runs any shell command inside the computer viaPOST /computers/{id}/bash. The cleanest transfer is to pull your data in from inside the computer: no size limits, no laptop round-trip.
Recommended: via a Git repo. Push the state you want to keep to a private repo, then clone it inside the Orgo computer:
- Any URL. Host the tarball anywhere reachable and
curl/wgetit from inside the computer the same way. A Git repo is the tidiest, versioned option. - Small files (< 10 MB).
POST /files/uploaddrops a file straight onto the computer. It caps at 10 MB. For larger state, use the Git or URL pull above, or split into < 10 MB batches.
Set up on Orgo
One call provisions the computer. Install your software with the same/bash endpoint.
bash, exec, screenshot, click/type).
What’s different
Neutral, both directions:- Fly does, Orgo doesn’t: general-purpose compute and PaaS, with arbitrary long-running services, public inbound via Anycast shared/dedicated IPs, multi-region deployments, and opt-in persistence via Volumes (a Machine’s base filesystem is ephemeral).
- Orgo does, Fly doesn’t out of the box: a persistent GUI computer with a built-in agent-control API (screenshot / click / type), sub-second boot, and nothing to administer. You manage no OS, no firewall, and no TLS.
Reference
Fly Machines
Compute primitive
Fly SSH & SFTP
Extract files
Orgo Quickstart
Control a computer over HTTP
Move an agent (Hermes/OpenClaw)
Full state-preserving playbook