Skip to content
Docs menu

Venom Computers

A persistent browser for every agent, running on your own daemons, with logins that stay and a person who can take over for a 2FA code or a CAPTCHA.

View .md

Venom Computers gives each agent a browser of its own. The browser keeps its cookies, logins and files between runs, so an agent that signed in once is still signed in tomorrow. It runs on a daemon you own, not on someone else's sandbox service, and the laptop of the person who set it up can be closed.

In this section

  • Agents on computers: Give a Chat agent or a Tasks agent a computer. Its mentions and delegations then run on its own browser on your daemon, ask you before risky actions, call you in for a login or a CAPTCHA, and stop at their daily limit.
  • What a computer is: A computer is one agent's persistent browser on one of your daemons. How it is placed, started and stopped, who can see and control it, and what the cloud keeps about it.
  • 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.
  • Run Computers on your own daemon: What a daemon needs to host Venom Computers: Docker, RAM and disk sizing from the measured numbers, the venom-computer image (published and digest-pinned, or built locally), the compose profile, a reachable endpoint for the live view, Chromium updates, and Kubernetes.
  • The Computers app: Watch every agent's computer in one fleet view, open a live view, take control for a login or a CAPTCHA and hand it back, and choose whether a computer is dedicated to one agent or shared by several.
  • Computers for agents: The computers_* MCP tools and the REST API behind them, who a call acts as, and what an agent may do with its own computer and the shared ones it belongs to.
  • Routines: Run a Chat or Tasks agent, or one of your bots, on a schedule, when an email arrives or when a webhook is called, and keep every run with its status, cost and result.
  • Desktop computers: A computer that is a full Linux desktop instead of a browser alone, with a terminal, a file manager and any app in the image. What it costs, how to run one, and what an agent can do on it.
  • Capacity and sizing: What one daemon holds, measured with the Computers load test. Memory per active browser, how many run at once, resume time, tool-call overhead, burst behaviour, and how to run the test on your own machine.
  • Saved logins and cards: Save a login, a card or a text once, and an agent types it into pages on its computer without ever seeing it. Where values are stored, which pages may receive them, and how to revoke.
  • Sharing a computer: Let several agents use one browser so a site is logged into once, with turns on a shared tab, using WhatsApp Web as the example.
  • Watch a computer and take control: How Watch and Take control reach a computer with nothing to set up (WebRTC straight to the daemon, even behind NAT), what the STUN server sees, when a TURN server is needed (yours or a managed one), the direct and snapshot fallbacks, the control lease, and how an agent asks for a person.