Skip to main content
Every bot can have a computer. In the web app it is an isolated Cloud guest with a desktop, and the Computer rail on the right of the open bot shows that desktop live while the bot works.

​
Hosts

The browser cannot choose This PC or SSH; that is host placement, not a missing option. A Cloud bot still has a full desktop and a shell.

​
Open desktop and Sleep

1

Open a bot you own

Guests cannot drive a bot.
2

Choose Open desktop

The guest starts. The rail reads Connecting only while the guest is starting.
3

Watch it work

The live screen shows what the bot sees and does — pages it opens, controls it clicks, files it edits.
4

Choose Sleep when you are done

The guest hibernates. The next active turn wakes it before the model is prompted, so the bot never has to apologise that it has no shell.

​
Rail states

​
What the bot can do on its computer

The computer-use tools let the bot look (screenshot), point precisely (grounded_click), type, press hotkeys, scroll, drag, wait, open and switch apps, save a note, and hand a coding task to code_agent. The planner describes the control it wants; a second inference call returns the exact framebuffer coordinates, so the planner never guesses raw pixels. A browser tool and a shell round it out. Full list: Tools. Dangerous computer steps park behind Approvals before they run.

​
Three machines, again

A bot’s desktop cannot see a Code repository, and a Code session cannot reach a bot’s screen. See Security.

​
Related