Use this file to discover all available pages before exploring further.
Orgo gives an AI agent a full Linux cloud computer to operate — desktop, browser, shell, files, and a built-in HTTP control API. This guide moves Hermes Agent or OpenClaw from DigitalOcean, Fly.io, or Hetzner onto an Orgo cloud computer with memory, skills, sessions, and configuration preserved.
Orgo is purpose-built for agents that operate a desktop, browser, or any app without a programmatic API. Pure headless backend scripts are equally well served by a VPS.
Tarball is typically 5 MB to a few hundred MB depending on session and media-cache size.
2
Create the Orgo computer
curl -X POST https://www.orgo.ai/api/computers \ -H "Authorization: Bearer $ORGO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"workspace_id":"WORKSPACE_ID","name":"hermes-prod","ram":8,"cpu":4,"disk_size_gb":32}'# → save the returned id as $COMPUTER_ID
3
Transfer the tarball in
Pick the source platform tab in Transfer the tarball. End state: /root/Desktop/hermes-state.tgz exists on the Orgo computer.
4
Install Hermes
Run any shell command in the VM via POST /computers/{id}/bash. For interactive work, orgo ssh hermes-prod opens a live terminal.
curl -X POST https://www.orgo.ai/api/computers \ -H "Authorization: Bearer $ORGO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"workspace_id":"WORKSPACE_ID","name":"openclaw-prod","ram":8,"cpu":4,"disk_size_gb":32}'# → save the returned id as $COMPUTER_ID
3
Transfer the tarball in
Pick the source platform tab in Transfer the tarball. End state: /root/Desktop/openclaw-state.tgz exists on the Orgo computer.
If you have SSH, you have a path: tar the state dir → scp to your laptop → curl to /files/upload. If the source can reach the public internet, skip the laptop step and curl directly from the source.
Don’t run two gateways on the same bot token. Stop the source gateway first, verify on Orgo, then delete the source. Two live gateways race for incoming messages.
hermes setup rewrites .env. Run the restore step after install. Don’t re-run the wizard or it overwrites the API keys you brought over.
sqlite needs disk headroom.fsync returns EIO (Errno 5) on a full disk. Size the computer with at least 2× the source state-dir as free disk.
Device-bound pairings re-pair. WhatsApp Web, iMessage, Signal. Re-scan the QR on Orgo.
Repoint webhooks at https://{instance_id}.orgo.dev/<path>. The hostname is stable across stop/start.
hermes doctor only confirms the binary is wired. To prove memory restored correctly, ask the agent something only it would know:
Hermes
OpenClaw
curl -X POST https://www.orgo.ai/api/computers/$COMPUTER_ID/bash \ -H "Authorization: Bearer $ORGO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"command":"hermes chat \"What did we last discuss in our previous session?\""}'
The reply should reference real context from the source machine. Generic answers (“I don’t have memory of past chats”) mean ~/.hermes/sessions/ or ~/.hermes/memories/ didn’t restore — re-check the tar xzf step and that you didn’t extract before the install step ran.
curl -X POST https://www.orgo.ai/api/computers/$COMPUTER_ID/bash \ -H "Authorization: Bearer $ORGO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"command":"openclaw send self \"What was our last topic?\""}'
If the reply has no continuity, inspect ~/.openclaw/workspace/ to confirm sessions and skill files copied across.
Most common cause: .env lost its 0600 mode during transfer, or hermes setup ran a second time and overwrote it. Restore from the tarball, then chmod 600 ~/.hermes/.env.
sqlite returns 'database is locked' or fsync EIO
df -h / # disk full?lsof | grep '\.hermes/.*\.db' # another process holding it open?
If disk is at 100%, the in-VM gateway can’t write checkpoints. Bump disk_size_gb with a live resize:
Wait 30 s, then re-test from the messaging client. If still silent, check the gateway logs on Orgo for unauthorized-shaped errors — the bot token may have been rotated between snapshot and restore.
WhatsApp QR won't load
The pairing in ~/.hermes/whatsapp/ is bound to the old device’s hardware fingerprint. Wipe it and re-pair: