A cloud desktop for AI agents

"Give the agent a computer" has become a category, and the phrase now covers four quite different things. Here is what a cloud desktop for an agent is, what it is not, and what it has to include before it is worth paying for.

A year ago an AI agent lived in a chat window. Now most serious ones get some kind of machine — a container, a browser session, a virtual desktop — because the useful jobs happen on real software behind real logins, not in a text box. The trouble is that "a computer for your agent" is sold by developer tools, browser products and consumer apps alike, and they mean different things by it.

Four things that get called a computer for an agent

An ephemeral sandbox

A container that exists for one task and is destroyed afterwards. Excellent for running code safely; useless for anything that needs to persist. Every task starts logged out, with no files and no history. Most general-purpose agents run on this, which is why they cannot remember what they did yesterday.

A browser session

A headless or remote Chrome the agent drives. Good for web tasks; it is a browser, not a computer — no desktop, no files outside the download folder, no other applications. And it is usually ephemeral too, so the same login problem applies.

A developer VM

Infrastructure products sell "computers for agents" to people building agents: an API that boots a VM, streams a screen and accepts clicks. Genuinely powerful, and the right foundation if you are writing an agent yourself. If you are not, it is a building site, not a house — there is no agent in it, no memory, no mail, nothing for a non-developer to use. See how to give an AI agent its own computer for how these approaches compare in detail.

A persistent desktop with an agent already at it

A real operating system with a window manager, a real browser, a file system, its own email address — provisioned once, kept running, and used by an agent that comes with it. You describe the job in chat; the agent works on the machine; you watch the screen streamed to your browser and take over whenever you want. This is what MyClawn is, and the rest of this page is about what that category has to include to be worth the name.

What a cloud desktop for an agent has to include

• Persistence. The same machine tomorrow: files stay, logins stay, installed apps stay. Without this it is a sandbox with a wallpaper.
• A live screen. The desktop streamed to you as it happens — not a summary, not a log of tool calls. This is what makes the agent's work checkable while it is still happening.
• A real handover. Click in, and the keyboard and mouse are yours; hand back, and the agent continues. Without it the agent has to refuse every login, CAPTCHA and consent screen — or guess.
• An identity of its own. Its own email address and its own sessions, separate from yours, so what it does is done as itself and can be audited as such — see giving an agent its own email address.
• A stop button. The human is priority one. Interrupting must be immediate.
• Isolation. One customer's machine cannot reach another's. The guarantees, as implemented, are on the Security & trust page.

What it costs, and why

A real machine has to exist for you all the time, so this costs more than a chat subscription. On MyClawn a dedicated desktop starts at $19 a month (2 GB RAM, 20 GB disk, AI usage credits included), with larger tiers for heavier work; the browser-only agent is free to start so you can try the chat and memory before there is a machine at all. The full table is on Pricing & credits.

What still breaks

• Heavy desktop software. A 2 GB machine runs a browser, a mail client and office tools comfortably; it will not run a video editor. Size the tier to the job.
• Sites that ban automation. A real browser passes most checks, not all. Read the terms of anything that matters to you.
• The first login is yours. The agent starts logged into nothing. You hand it each portal once, on its screen — after that the session persists.

Where this is the wrong tool

If you are building an agent, buy the developer VM and build on it. If your tasks are one-off and attended, a browser extension in your own browser is faster and often free. A persistent cloud desktop with its own agent is for the person who wants the work done for them, on a machine they can watch, that keeps going after they close the laptop. You can watch one work and take over before deciding.