What one agent is
Its own machine
One virtual machine and one block volume per agent. Nothing is pooled with
another customer’s agent.
Its own provider key
Each agent gets a separate model key with a spending limit on it. The limit
is what stops a runaway agent, not a support ticket.
Its own disk
The workspace survives restarts, redeploys and version upgrades. It is the
agent’s memory of what it has been doing.
Reachable four ways
The Control UI in your browser, Telegram Hub, any channel you set up inside
OpenClaw, and a shell.
Start here
Quickstart
Account to running agent, in the order the screens ask for it.
What you pay for
The seat and the balance are two different things. This is the page that
explains why.
Inside the agent
The Control UI is where the agent is actually used. Channels and skills live
there.
Stopping a runaway
Four separate things pause an agent on their own. Here is what each one
watches.
What the platform does not decide for you
The agent’s behaviour is not configured on this side. There is no wizard that asks which skills to enable, and no screen in the panel that pairs a Telegram bot to an agent. Those choices belong to OpenClaw and are made in the agent’s own interface — see Inside the agent. The one exception is Telegram Hub: a single platform bot that reaches every agent on your account, which exists because it needs an account-level link that no individual agent can hold.The interface is available in ten languages. This documentation is English
only.