Skip to content
Docs menu

Enable Computers on a daemon

One click turns Venom Computers on for a daemon, from the Computers app, the daemon page or the daemon's own dashboard. What it checks, how long it takes, what the error messages mean, and the MCP tools and REST routes behind it.

View .md

Computers run on your own daemons. You do not build an image or set an environment variable: click Enable Computers on this daemon and the daemon does the rest. On Linux the daemon installer does it for you when Docker answers, and venom-daemon computers on does it from a terminal.

Where the button is

  • Computers app. When none of your daemons hosts computers yet, the empty state lists the daemons that could, each with its button.
  • Daemon page. Console → Daemons → the daemon → Computers.
  • The daemon's own dashboard. On the machine itself, Local models → Computers.

Only organisation owners and admins can use the cloud buttons, and every use is written to the audit log (computers.daemon_enabled, computers.daemon_disabled). The daemon must be online and recent enough to report that it can host computers; an older daemon says so and asks you to update it.

What happens

  1. Checks. Linux; not inside a container; Docker installed, running and usable by the daemon's user; at least 10 GiB free where the daemon keeps its data; at least 4 GiB of RAM. Each failed check shows one sentence that says what to do (for example "Your user cannot use Docker. Run sudo usermod -aG docker $USER, then log out and back in."). macOS is not supported yet and says so.
  2. Image. A daemon installed from a release builds the venom-computer image on the machine from the files it ships in share/computer/ (the Dockerfile and a prebuilt venom-seatd; Docker downloads the Debian base and Chromium). The tag is venom-computer:b- and a hash of those two files, so an update that changes them builds the new image at the next start and one that doesn't reuses the old. Once the new image runs, the daemon removes the older venom-computer:b- images that no container uses (about 1 GB each). A daemon run from a source tree builds venom-computer:dev from it, and a release that carries a published digest-pinned image pulls it instead. The first time takes a few minutes.
  3. Saved setting. The choice is written to computers/setting.json in the daemon's data directory, so it survives a restart.
  4. Start. The daemon starts the computers manager without restarting. Within seconds its heartbeat reports capacity and the cloud can place computers on it.

After a reboot the daemon turns Computers back on by itself. When it starts before Docker does (start at boot), the card says "Waiting for Docker to start" and it goes on as soon as Docker answers, for up to five minutes.

If a step fails, the card shows Needs attention with the reason, and the button stays so you can try again after fixing it. Turn off hibernates every computer on that daemon (their profiles and logins stay on disk) and stops hosting.

VENOM_COMPUTERS=on in the daemon's environment still works and wins: the card then says it is on because of the variable, and Turn off is not offered. See Venom Computers on a daemon for capacity and the advanced settings.

For agents and scripts

Tool REST What
computers_daemon_list GET /api/workspace/computers?extras=1 (the setup list) Daemons that report Computers setup: online, hosting, state, whether they can be enabled
computers_daemon_enable POST /api/workspace/computers/daemons/{id}/enable Send the enable job; answers at once, read the list for the outcome
computers_daemon_disable POST /api/workspace/computers/daemons/{id}/disable Turn it off

The two write tools need an organisation owner or admin. The daemon's own admin API has GET /admin/v1/computers, POST /admin/v1/computers/enable and POST /admin/v1/computers/disable; enable answers 202 while it works and 200 once on. On the machine, venom-daemon computers on|off|status calls them and prints each step.