Cua

Letting the agent loose on the user's host is a security non-starter — the LLM hallucinates a rm -rf, exfiltrates a credential, or installs a payload. Spinning up a desktop VM is the obvious answer, but every team building one ends up rebuilding the same six layers: Apple Virtualization Framework wiring, screen capture, input simulation, container orchestration, isolation policy, and a hot-start runtime that boots fast enough for a chat-speed agent loop.^[1]

Browser agents got a head start because the browser is already a sandbox. Browser Use commoditized the agent framework on top (50k+ stars).^[13] Browserbase took multiple rounds of funding to build managed browser infrastructure underneath.^[5] But the browser is a subset — Anthropic and OpenAI both shipped computer-use APIs at the OS level precisely because the bulk of real work happens outside the tab.^{[7] [4]}

There is no Browserbase for the desktop. Every team trying to ship a CUA-class product is paying the infrastructure tax in-house — and the tax is high enough that some give up and ship browser-only. Cua is the missing primitive: one command, MIT-licensed Linux, macOS, Windows, or Android container, exposed through a computer-use interface any LLM can drive, running at 97% native CPU on Apple Silicon.^{[1] [2]}

Frontier labs validated the API surface. Anthropic shipped Claude 3.5 Sonnet computer use in October 2024 — 14.9% on OSWorld, nearly 2× the next-best system, and partnered with Replit, Canva, Asana, DoorDash, Cognition, and The Browser Company on launch day.^[7] OpenAI followed three months later with Operator at 38.1% on OS-level tasks.^[4] The category went from research demo to production primitive in twelve months.

Vision-language models hit the latency floor. Sub-second screen reasoning is now table stakes — Claude Haiku, GPT-4.1 mini, and a wave of open multimodal models cleared the bar. The bottleneck moved from model to runtime. Container boot time, snapshot/restore, and image distribution are now the rate-limiting steps in an agent loop, and they are exactly the surface Cua engineers against.^[1]

Developer demand outran the infrastructure. 17.8k GitHub stars on Cua's OSS core, 50k+ engineers using the platform, a 600+ developer Discord, and parallel multi-agent products (Codex, Claude Code's parallel execution) that already spin up multiple desktops concurrently.^{[1] [2]} The orchestration problem isn't a future bet — it's a present-tense one.

Hot-start under one second. The managed cloud snapshots a warm desktop image and restores it for every new agent session. The cost difference between a cold-boot VM and a hot-start image is roughly 60× — the difference between a runtime you can spin up per chat turn and one you can't.^[2]

Cross-OS fleet orchestration. macOS, Linux, Windows, and Android containers from one control plane. Windows desktops in particular are exclusive to the cloud — Apple Silicon licensing makes self-hosting Windows impractical for most teams, which makes managed the only path for the workloads that actually require it (legacy ERP, .NET, native enterprise tooling).^[2]

Observability, recording, and replay. Every agent action recorded as a video plus structured trace. The artifact stack is what turns an agent prototype into a production workload — eval harnesses, regression testing, incident debugging. The OSS gives you a container; the cloud gives you a system.^[2]

The runtime stops being a moat the moment it becomes a standard. Docker the company didn't capture the orchestration value — Kubernetes, registries, and the hyperscalers did. Cua's thesis is to be the OSS standard at the runtime layer and the first mover at the orchestration layer. Browserbase ran the same play in browsers and built a real business on it.^[5]

The operational memory compounds. Every agent run leaves a trace inside the container — what worked, what failed, which UI surfaces broke, which recovery strategies converged. That dataset is the natural input for RL training, regression evals, and reliability improvements. Cua-Bench is already in the repo for exactly this loop.^[1]

The container is the API contract that survives model churn. Frontier models cycle every six months. The OS surface doesn't. A team that builds against Cua's computer-use interface today will run the same code against whichever model is best in 18 months. Abstraction over substrate is the durable position.

Near-term ICP is every team shipping a computer-use agent: foundation labs running evals (HUD, on the customer list), legacy automation startups (Fira), academic research, YC AI cohort companies, and the 50k+ engineers already building on Cua.^[2] The buyer is a technical founder writing a research preview, or a Series-A team scaling fleet ops — both want OSS by default and managed when production demands it.

Longer-term, the category is agent infrastructure as a line item. RPA is a ~$22B (2024) market growing toward $90B+ by 2030, driven by enterprise digitization.^[6] The CUA-class agent stack is the AI-native successor — the segment where workflows RPA can't reach (legacy ERP, design tools, CAD, native apps with no API) finally become automatable. Browserbase has proven a real business sits under browser agents; the OS-level fleet is structurally a larger surface.