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.
The Computers app is where people look after the computers agents work on. It lives at /computers in the console (one computer opens at /computers/{id}), on
the rail next to Chat, and needs the computers add-on (included in Team and up). Owners and admins manage every computer,
developers create and use them, billing members and viewers can look.
The fleet
The fleet is one card per computer: its name, the agent it belongs to, a state chip, when it was last active and the daemon that holds it. Needs you computers sort first, then running ones, then the ones asleep.
| Chip | Meaning |
|---|---|
| Not started | Only the profile exists. |
| Starting | The daemon is opening the browser. |
| Queued (3 ahead) | The daemon is full. The computer waits its turn, first in first out. |
| Active / Idle | A browser is running; active means the agent is doing something. |
| Hibernated | The browser is closed, the logins and files are kept. |
| Needs you | The agent asked a person to take over (a login, a code, a CAPTCHA). |
| Daemon offline | The daemon has not checked in. Computers on it cannot be shown. |
Above the cards each daemon shows its capacity: how many computers are active out of its limit, how many seats it holds and how many are queued. Filter by text, state, agent or daemon. A hundred computers stay smooth: the grid draws only the rows near the screen.
Cards show a live thumbnail only while they are on screen, at most once every five seconds, and not while the tab is in the background.
Keys: c new computer, / filter, j and k (or the arrows) move, Enter opens. The shortcuts sheet (Ctrl+/ or
Cmd+/) lists them.
If no daemon hosts computers yet, the page says so and links to what a computer is, which
explains how to start one with VENOM_COMPUTERS=on.
One computer
Open a card for the live view, Activity and Details.
The live view draws the computer's screen from the daemon straight to your browser, with the frame rate and the delay between your last input and the picture that followed shown in the corner next to its mode, Live. The view tries the daemon's own WebSocket first. When the daemon is not reachable from your browser, the cloud relays a still picture instead (Snapshots every 2 s) with a note, and taking control is not offered. The view is built on a small transport interface, so a further path (WebRTC, shown as Live or Live (relayed)) slots in between the two.
Take control (t) gives you an exclusive five-minute lease, renewed while you are on the page. While you hold it, the
agent's input tools wait and it may still read. Your mouse, wheel and keyboard go to the computer, including text from an
input method (Chinese, Japanese, Korean) and pasted text. Release with the button, r, or Ctrl+Alt+R from inside the
view. Leaving the page releases it too. On a phone a tap is a click, dragging scrolls, and the Keyboard button opens
the on-screen keyboard.
Needs you. When an agent asks for a person, the computer shows what it needs. Take control, do it, and press I'm done, or press Skip if it no longer matters. Either hands the computer back to the agent.
Start wakes a hibernated computer. Hibernate closes its browser and keeps its profile.
Activity lists what the agent did, newest first, and updates by itself: pages visited, downloads, approvals and handovers. Typed text and secrets are never recorded. Details shows the kind, daemon, where it runs and who uses it.
Keys: t take control, r release, s start, h hibernate, a the side panel, , settings, Esc back to the fleet.
Dedicated and shared computers
Open Settings (,) on a computer, or choose when you create it.
- Dedicated is one agent with one browser, so its logins stay its own. This is the default.
- Shared lets several agents use one browser, so a site is logged in once. WhatsApp Web, which allows only a few linked devices, is the usual reason. Pick Shared, save, then add the agents under Agents on this computer.
Agents on a shared computer share its logins and can use its shared tabs, so only add agents you trust with every account signed in there. A computer cannot go back to dedicated while it has agents; remove them first. An agent can have its own computer and belong to shared ones.
Settings also holds the name, Host of its own (a computer in its own container, apart from the others, which uses more memory) and Delete computer, which removes the profile, logins and files from the daemon.
Try it without a daemon
Add ?demo=1 to a computer's address. The live view then draws a test pattern instead of a daemon's screen and shows
your clicks, scrolls and keys on it, so you can try the view, the keyboard and taking control. Everything else on the page
(the lease, Needs you, Activity) is real; the picture is a drawing, and says so.
For developers
The app uses the workspace REST routes in Computers for agents, and GET /api/workspace/computers?extras=1, which adds each daemon's capacity, the agents a computer can name and the caller's
level. The live view asks POST /api/workspace/computers/{id}/screen with {scope: "view" | "control"} for
{endpoint, ticket, mode} and opens wss://<endpoint>/computers/{id}/screen?venom_ticket=…: each binary message is one
JPEG frame, and input goes back as text messages {"method": "Input.dispatchMouseEvent" | "Input.dispatchKeyEvent" | "Input.insertText", "params": {…}} on a control connection only. Without that route or a reachable endpoint the view uses
GET /api/workspace/computers/{id}/frame (the newest relayed thumbnail). The design is in
ADR 0078 §6.