Agents

Use Agent Computer to run coding agents on one machine, inspect live work on that machine, or expose a remote session through ACP.

Agent sessions

Start by listing the agents available on a machine, then create or resume a session with the agent, name, and working directory you want to keep stable.

$ computer agent agents my-machine

$ computer agent sessions list my-machine

$ computer agent sessions new my-machine --agent codex --name review

$ computer agent prompt my-machine "fix the failing tests" --agent codex --name review

$ computer agent watch my-machine --session <session-id>

$ computer agent status my-machine --session <session-id>

If you omit --cwd, Agent Computer uses the machine workspace. Managed workers now default to /workspace-<workspace>. Isolated machines back that path from their private worker data directory. Shared-home machines back it from /home/node/workspace-<workspace>.

ACP and skills

Use computer acp serve when you want a local ACP client to treat a remote machine agent like a local ACP process.

$ computer acp serve my-machine --agent codex --name review

$ npx skills add harivansh-afk/agentcomputer-delegate

computer-acp is for ACP bridging through computer acp serve.

Runtime

The agent harness inside every managed worker is built on Rivet's sandbox-agent. It handles process lifecycle, environment setup, and communication between the machine and the Agent Computer control plane. You do not need to install or configure it yourself - it ships as part of the managed worker image.