Computers
A Computer is a durable cloud desktop. It gives each user, agent, or workflow a real Linux GUI with browser state, files, shell access, desktop streaming, and programmatic control. Use it when the work depends on pixels, sessions, browser logins, desktop apps, accessibility trees, or a human taking over the same machine an agent was using.
For pure code execution, builds, and preview servers, Sandboxes are cheaper and faster. For a 24/7 production web app, use App Engine. Still deciding? See Computers vs sandbox.
1. Create a Computer
Pass external_workspace_id to attribute the Computer to one of your tenants.
See Lifecycle and sizing for states, sizes, and workspace scoping.
2. Drive the desktop
Start each loop with an observation, act once, then observe again. The full action set is in Computer use.
3. Watch it live
A Computer is also a live pixel stream. Open it from the MIOSA console, or embed the same stream in your app with a short-lived URL minted on your backend.
const urls = await computer.urls()
console.log(urls.desktop_url) See Embedding and streaming for the token and iframe flow.
Pick what you need
| You want to | Start here |
|---|---|
| Create, size, and manage the machine | Lifecycle and sizing |
| Choose a Computer or a Sandbox | Computers vs sandbox |
| See what ships in the box | Inside a Computer |
| Drive the desktop from code | Computer use |
| Embed the live desktop in your UI | Embedding and streaming |
| Ship it safely | Production checklist |
| Measure startup | Fast start and readiness |
Next
Pick the right machine for the workload, with the rule of thumb.
What ships in the box and how the desktop, disk, stream, and API fit together.
Fast startup, the state machine, resource sizes, and workspace-scoped creation.
Access model, the operator workflow, and embedding the live desktop in your UI.
The defaults to verify before you rely on a Computer in production.
Full action reference: screenshot, click, type, key, scroll, drag, windows, accessibility tree.