Agent X
Paid
E-commerce and retail businesses
Generic sandboxes boot one OS, reset state manually, and hand you a single machine — fine for smoke tests, not for parallel RL rollouts across Linux, Windows, macOS, and Android simultaneously. Cua is the infrastructure layer built for exactly that gap.
$15/mo · Free tier: Up to 2 computers in use at once and 20 remote hours a month · Checked Nov 13, 2026
Cua provisions cross-OS fleets from a single API, forks machine state over copy-on-write snapshots so you can reproduce failures without rebuilding from scratch, and serves pre-booted machines from warm pools that claim in milliseconds. The open-source Cua Driver runs background desktop automation on macOS and Windows — agents click, type, scroll, and inspect accessibility trees without stealing your cursor. Linux support in Cua Driver is in pre-release, so teams with Linux-heavy desktop workflows will hit that wall immediately. At scale, you either point your training loop at live warm pools or order verified trajectory datasets that arrive pre-packaged for your ingestion pipeline.
Bottom line: Cua is the right call when you need parallel agent evals across four OS families with snapshot-based rollback — it breaks down as your primary surface when the desktop automation you need runs on Linux, where the Driver is still pre-release.
No account needed to start. Spaces on every computer you connect. Teleport. Share a Space with named people.
For one person. 2 months free when billed yearly. Cancel within 14 days of first yearly charge for full refund.
For a team that shares its computers. Per seat pricing. 2 months free when billed yearly. 1 to 100 seats. Cancel within 14 days of first yearly charge for full refund.
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
More options in Workflow Automation. Compare pricing, platforms, and features side by side.
Paid
E-commerce and retail businesses
Freemium
Content creators needing repeatable AI workflows
Most agent eval infrastructure treats a single VM as the unit of work. Cua treats a fleet as the unit. The core workflow is: boot machines across Linux, Windows, macOS, or Android via the Python or TypeScript SDK or the cua CLI, fork known machine states using copy-on-write snapshots, run parallel episodes across warm pools, and release machines back when the episode ends. Reward collection, failure reproduction, and dataset export all happen against the same fleet layer.
The differentiating feature is snapshot-native rollouts. Rather than tearing down and rebuilding a machine after each episode — the standard approach that serializes your batch throughput — Cua forks from a known snapshot, runs the rollout, and discards the fork. The vendor states warm pools scale to zero when idle and claim in milliseconds, which means large parallel batches do not wait on cold-start overhead.
Cua Driver, the open-source MIT-licensed component, is the piece that sits closest to your agent’s tool calls. It runs as an MCP stdio server, a long-running daemon, or a one-shot shell command on the same binary — so the same harness serves both automated agent loops and manual human testing. Native desktop backends on macOS and Windows preserve the user session, meaning the agent operates in the background without interrupting whoever is logged in. Linux support is explicitly in pre-release, which limits the Driver’s usefulness for teams whose target surface is Linux desktop.
For teams that do not want to manage the harness at all, Cua offers verified trajectory datasets: the vendor runs the rollouts on the same environments and delivers pre-packaged, evaluator-scored trajectory data scoped by task and surface. BYOC and on-prem options are available for teams with data-residency requirements, and the vendor states SOC 2 readiness for the hosted offering.
Sign in to rate this tool or suggest an edit.