Remote computers
The third layer is runtime computers. One personal gateway can register many runtime computers (gateway 1 : N). Tools run on the gateway host by default; shell/file tools can also target another host running sandbox-agent (HTTP).
While the gateway stays running, the Personal Agent can keep serving; work can land on the runtime machines registered under that gateway. On the client side, one client can switch among many gateways (see Service gateway).
UI: Settings → Gateway → Gateway service → Computers (formal label: Computers / 电脑连接).
Register computers
List header: computer name / Add computer.
- Local is always listed (no delete / probe toggle).
- Remote: name / host / port / token (
SANDBOX_TOKEN). Save runsprobeComputer: health must reportokbot-sandbox-agent, then a token probe against the shell API. Failed probes are not written. - Disable a remote row to exclude it from the default picker and routing.
- Pick exactly one default computer (local or an enabled remote).
Computer lists live on the gateway host; the client’s Gateway list only chooses which host to attach.
Routing (brief)
- Default computer from settings; empty = local
- Per-turn computer id, or name a computer in the message
read_skilland image generation stay on the desktop / gateway host — they do not follow computer switches
Remote protocol: health, shell (optional SSE), file read/write/edit. Suitable for cloud hosts, lab machines, or containers. A bare-metal sandbox-agent process can still be registered as a remote runtime computer.
vs switching gateways
- Gateway list (client): which Personal Agent host the UI attaches to (client 1 : N gateways, one active)
- Computers (gateway): which runtime computers that host can route tools to (gateway 1 : N)
Content is derived from the OkBot product repo and evolves with the product.