Skip to main content
OpenClaw
OpenClaw is an open-source AI agent that runs on a computer, controls applications, automates tasks, and connects to messaging platforms through a gateway. This guide installs OpenClaw inside an Orgo cloud computer.

​
Why run OpenClaw on an Orgo computer

The agent and its skills live on the cloud computer. Other devices connect to it.

​
Isolation

OpenClaw is designed to take actions on a computer: install skills, run shell commands, control applications, hit APIs with your credentials. On a personal laptop that means the agent has the same access you do, including your home directory, browser sessions, SSH keys, and ~/.aws/credentials. On an Orgo computer the blast radius is that computer. The agent has access to whatever you install or paste into it and nothing else. Delete the computer and the state is gone.

​
Install

1

Create the computer

Open orgo.ai/workspaces and create a computer with at least 8 GB RAM.
2

Open a terminal on the computer

Open the computer in the dashboard and launch Terminal from the taskbar.
3

Run the installer

The installer detects the OS, installs the openclaw CLI, and starts the onboarding wizard. The wizard configures a model provider, API key, and gateway port (default 18789).OpenClaw needs Node 22.22.3+, 24.15+, or 25.9+. On Linux the installer provisions Node 24 LTS when Node is missing.
4

Run the gateway in the background

An Orgo computer does not run systemd, so openclaw onboard --install-daemon cannot register a service there. A detached tmux session keeps the gateway running after you disconnect, but it does not come back on its own after a restart. For a gateway that restarts on crash and on boot, launch the curated OpenClaw template instead.
5

Verify

Run openclaw dashboard on the computer to open the Control UI in its browser. The gateway itself listens on port 18789.

​
Install via the Orgo SDK

Drive the install from your laptop. Every computer.bash(...) call runs on the cloud computer.
Set ORGO_API_KEY on your laptop and add ANTHROPIC_API_KEY to the workspace’s Secrets first. Apply secrets copies it onto the computer, so the key is never sent in a command: request bodies sent to Orgo’s API are logged. State lives in ~/.openclaw/ on disk and survives restarts. The tmux session does not, so start the gateway again after a restart, or use the curated OpenClaw template, whose gateway restarts on its own.

​
Gateway

The gateway accepts messages from Discord, iMessage, Matrix, Microsoft Teams, Signal, Slack, Telegram, WhatsApp, and other platforms. The onboarding wizard configures channels on first run. To change them later:
A computer has no public inbound hostname. Run gateways in outbound/socket mode (for example Slack Socket Mode or Telegram long-polling). The authenticated proxy at https://www.orgo.ai/api/desktops/{instance_id}/proxy/<path> reaches the computer’s Desktop API only, not the gateway port, so it cannot deliver webhooks to the gateway.

​
Installing skills

OpenClaw skills are distributed through ClawHub:
Skills install into ./skills under the current working directory, and installed versions are recorded in .clawhub/lock.json. Set CLAWHUB_WORKDIR to install somewhere else. Run the commands from a fixed directory on the computer so the skills persist across restarts.

​
Sizing

One computer is capped at 4 vCPU and 64 GB RAM, and your plan may cap it lower. See Instance types. The curated OpenClaw template runs on 1 vCPU and 8 GB RAM.

​
Tips

  • Config and gateway state live in ~/.openclaw/. Skills live wherever you ran clawhub install.
  • Watch the gateway’s output with tmux attach -t openclaw. Detach with Ctrl+B, then D.