Skip to main content
Computer is agent-only. It never appears on an MCP gateway or in a workflow — enforced by its exposure scope and again by its own tool listing.
Computer gives an agent a machine of its own. One agent, one Computer, shared across that agent’s sessions and alive between turns — state you leave behind is still there next time.

​
The tools

Five always-on tools: Eight more when the browser subsystem is enabled: computer_browser_status · computer_browser_navigate · computer_browser_snapshot · computer_browser_act · computer_browser_screenshot · computer_browser_pdf · computer_browser_tabs · computer_browser_close
Computer is a shell and browser capability. There is no desktop screenshot, no mouse coordinate control, and no keyboard-event API.

​
Sizes

The OS image is fixed by the platform, not chosen per Computer.

​
Per-binding configuration

Browser tools list only when the browser subsystem is enabled and its navigation allowlist is non-empty. An empty allowlist does not mean “all domains” — it means the browser tools are suppressed.
The machine id is set automatically when the Computer is provisioned; you do not supply it.

​
Limits

​
Cost

Metered hourly, scaled by size — x4 costs twice x2, x32 sixteen times. A Computer that is up but idle still costs. Deleting the agent deprovisions its Computer. See noorle.com/pricing.

​
Autonomy

Privileged tier, every tool. At Supervised it pauses unless auto-approved; at Read-only it is denied. A Privileged allow that cannot be written to the audit trail is converted to a deny. Because Computer is agent-only, those pauses can actually reach a human — the Playground and AG-UI clients render them.

​
Computer, Sandbox, or Browser?

Use Computer’s browser when an agent needs to stay logged in across turns. Use the standalone Browser capability when each fetch is independent. Computer is agent-only — a workflow cannot bind or call its tools.

​
Next