LaunchedEditorial Listing

Cua

Cua AI, Inc. · Cua: Open-Core Computer-Use Infrastructure for AI Agents on macOS, Windows, and Linux

Open Cua

Cua is open-core infrastructure that gives AI agents real computers to operate: an MIT-licensed driver that lets Claude Code, Codex, Cursor, and other agents click, type, and read native apps on macOS, Windows, and Linux, disposable sandboxes on your own machines or cloud account, the Cua Spaces app for watching and taking over agent desktops (free, with paid Pro and Teams plans), and Cua Bench for evaluating computer-use agents. It suits developers adding desktop control to their agents and teams running computer-use evals, training, or data generation on their own infrastructure.

PricingFreemium
Setupmedium
Runs onDesktop · API · Self-hosted
APIYes
Open sourceYes
DocsYes
Computer UseAgent InfrastructureDesktop AutomationSandboxOpen SourceSource-AvailableSelf-HostedMCPHuman-in-the-LoopMultiplayerClaude Code

Best for

Developers who want their existing coding agent to operate native desktop apps without taking over their screen, and AI teams that need reproducible desktops on their own hardware or cloud accounts for computer-use evals, training, and data generation

Not ideal for

People looking for a ready-made assistant that does tasks for them without setup, teams that want Cua to host the machines (its cloud ended in October 2026), organizations that require a permissive license for every component, and anyone uncomfortable granting an agent accessibility and screen-recording permissions

Who it's for

Developers adding computer use to coding agents and AI products, and research and AI teams running computer-use evaluation, training, and data generation

Capabilities

  • Cua Driver (MIT) reads accessibility trees and window screenshots and clicks, types, scrolls, and drives browser tabs in native apps on macOS, Windows, and Linux, in the background where the OS allows it, with a separate agent cursor so the user keeps focus
  • One driver binary runs as an MCP stdio server, a long-running daemon, or one-shot `cua-driver call` shell commands, with Python and TypeScript SDKs for apps that embed computer use
  • Documented setup for Claude Code, Codex, Cursor, Antigravity CLI, OpenClaw, Hermes, OpenCode, Factory Droid, Qwen Code, Kimi Code, Pi, and the Claude Agent and Codex SDKs, plus an installable agent skill
  • Local models through Ollama or llama.cpp with a tool filter that trims context, and a text-only mode for models that cannot read images
  • Cua SDK (Python, TypeScript, and Rust; Swift and Kotlin not yet released) and the `cua` CLI create disposable Linux, Windows, and macOS desktops locally (Docker or Podman, QEMU, Lume, or Hyper-V), on machines running cua-spacesd, through E2B or Daytona, or in your own AWS, Google Cloud, Hetzner, or Modal account with the same code
  • Runs coding agents such as Claude Code, Codex, Gemini CLI, OpenCode, and Goose inside a sandbox, streams their events, and lets any client reattach later
  • Cua Spaces app for macOS, Linux, and Windows (preview): live desktop streams (in the Mac menu bar and notch), a separate cursor for you and each agent on the same desktop, file sending, and sharing a Space
  • Current Spaces apps, the CLI and SDK, and cua-spacesd connect over an end-to-end encrypted WireGuard mesh by default, so the relay cannot read the desktop stream, input, files, or teleport bundles, and `CUA_MESH=require` blocks any fallback
  • Teams plan with shared team computers, roles, and device approval, drawing on a pooled allowance of live sessions and remote hours
  • Teleport moves an app and, with per-item consent and Touch ID for secrets, its signed-in state (Chrome, Firefox, Slack, Discord, VS Code, Notion, Claude Code, and others) into a Space
  • Lume creates and runs macOS and Linux VMs on Apple silicon from a CLI, local HTTP API, or MCP server
  • Cua Bench runs verifiable computer-use tasks with evaluators and oracles, a task registry, and adapters for OSWorld-Verified, MiniWoB++, WebVoyager, and Online-Mind2Web
  • Published Linux, Omarchy, Windows, macOS, and benchmark images, most of which ship with cua-spacesd and Cua Driver preinstalled

Limitations

  • Not a finished agent: you need your own agent harness and model access, since Cua Driver never calls a model API
  • Cua does not host or rent computers: Cua Cloud and Fleets (managed pools, warm replicas, and the Terraform provider) ended on October 18, 2026, so desktops run on your own machines or in your own AWS, Google Cloud, Hetzner, or Modal account
  • In your own cloud account only Linux images are offered (Windows, Omarchy, and macOS are not, and Hetzner takes container images only), and an account holds at most 32 machines
  • Cua Spaces, and Cua Driver Bench from October 11, 2026, are source-available under FSL-1.1-MIT, not MIT: they cannot be offered as a competing hosted service, and each release becomes MIT two years after it ships
  • The Cua Spaces app needs macOS 26 or later on the Mac, supports only Ubuntu 24.04 on Linux, and is in preview on Windows; macOS Spaces need Apple silicon, and Lume allows at most two macOS guests at a time, Apple's limit
  • Linux driver support is toolkit- and compositor-dependent: X11 is supported with toolkit limits, Sway and GNOME with limits, and KDE and Hyprland are experimental
  • Browser viewers, web agents, share links, older versions (0.6.x and earlier), and fallback connections still use a relay path that terminates TLS and can read the session, and the relay always sees who connects to which machine and when
  • Teleporting a signed-in session gives whoever controls the destination Space a live sign-in, and Chrome saved passwords moved by teleport do not yet decrypt in a Space
  • The free Spaces plan covers 2 live sessions and 20 remote hours a month through the relay; SSO and audit export are not included yet even on Teams
  • Usage telemetry is on by default and linked to a random account ID when you are signed in; it can be turned off
  • Older packages (cuabot, cua-computer, cua-computer-server, and cua-agent) are no longer maintained, and Cua warns that cuabot has known security issues, so tutorials built on them are out of date

Use cases

  • Letting Claude Code or Codex build a desktop app and then operate it to QA the result
  • Giving an agent its own macOS or Linux Space with a teleported, signed-in Chrome session while you keep using your own Mac
  • Running computer-use evals in parallel on disposable Linux desktops in your own AWS, Google Cloud, or Hetzner account
  • Writing a verifiable desktop task in Cua Bench and scoring several agents or models against it
  • Starting a disposable Linux desktop in a GitHub Actions job to run GUI tests with screenshots
  • Turning a spare Mac mini into a host that your laptop and agents create Spaces on

Our take

Cua is worth a close look if your agent already writes code well but stalls whenever the job needs a GUI. The MIT-licensed driver is the most broadly useful piece: it plugs into the agents people already run and works in the background instead of hijacking the screen. Teams doing computer-use research get sandboxes and a benchmark harness from the same vendor, but since Cua Cloud and Fleets ended in October 2026 they now supply the machines, locally or in their own cloud account. Know which licence covers which piece, since Spaces is FSL rather than MIT, and check the platform matrix for the desktops you need. Treat Teleport and any relay path that is not end-to-end encrypted as trust decisions, not conveniences.

Who should use it

Developers who want Claude Code, Codex, or another agent to drive native apps and verify its own work, builders adding computer use to an AI product, and AI and research teams that need reproducible desktops for evaluation, reinforcement learning, or trajectory data.

Who should skip it

Non-technical users who want an assistant that just completes tasks, teams that only need browser automation, organizations that require permissive licensing for every component, and teams that want hosted machines, since Cua no longer runs a cloud.

Strengths

  • Driver, SDK, CLI, Lume, and Cua Bench are MIT-licensed and free to self-host
  • Works with the agents you already use through MCP, a CLI, or SDKs
  • Background control keeps your own cursor and focus while the agent works
  • One SDK covers local desktops, machines you own, and your own cloud account
  • Cua Spaces has a free plan and lets you watch an agent's desktop and take over

Weaknesses

  • You supply the agent harness and model, so it is not a ready-made assistant
  • Cua Spaces is source-available (FSL-1.1-MIT) rather than open source
  • No hosted cloud since October 2026, so you supply and pay for the machines
  • Linux coverage varies by toolkit and compositor
  • Teleporting signed-in sessions and some relay paths need careful trust decisions

Cua pricing

Open source

Free

  • MIT-licensed Cua Driver, SDKs, cua CLI, Lume, and Cua Bench
  • Local Linux, Windows, and macOS sandboxes
  • Self-host on your own machines or cloud account
  • Community support on Discord and GitHub

Cua Spaces Free

$0

  • Up to 2 live sessions and 20 remote hours a month
  • Spaces on every computer you connect
  • Teleport

Cua Spaces Pro

$18

Billed monthly

  • One person
  • Up to 5 live sessions and 200 remote hours a month
  • $15/month billed yearly ($180/year)
  • Expiring share links and 90-day audit history listed as coming soon

Cua Spaces Teams

$30 per seat

Billed monthly

  • 1 to 100 seats
  • Each seat adds 5 live sessions and 200 remote hours to a shared team pool
  • Shared team computers, roles, and device approval
  • $25 per seat a month billed yearly
  • SSO and audit export not included yet

Free tier limits: The open-source components have no usage limits. Cua Spaces Free includes up to 2 live sessions and 20 remote hours a month. Remote hours count each hour with at least one live session through Cua's relay, so using a computer from itself is free, and going over the allowance cuts nothing off; the app shows an upgrade notice instead.

Note: Cua does not host or rent computers: Cua Cloud and Fleets, previously billed per vCPU-hour and GiB-hour, ended on October 18, 2026. Spaces run on computers you own or rent yourself. In your own cloud account, Cua's docs estimate about $0.03 to $0.04 per hour on AWS or Google Cloud, about $0.0114 per hour on Hetzner, and about $0.24 per hour on Modal, billed by those providers. Cua's trust page says it received a SOC 2 Type I report in May 2026 and is working toward Type II. Plans and prices checked against cua.ai/pricing and Cua's docs on October 26, 2026.

Technical specs

Available models

Bring your own: the agent harness supplies the model (Claude via Claude Code, OpenAI via Codex, Gemini via Antigravity, Kimi via Kimi Code, Qwen via Qwen Code)Local models through Ollama or llama.cpp (tested with Meta Muse Glimmer 30B)CUA-S1-FORMS, an early research model for form-filling decisions

Where Cua excels

Having a coding agent QA the app it just built

With Cua Driver registered as an MCP server, Claude Code or Codex can launch the built app, click through it, read its accessibility tree, and check the result without taking over the developer's cursor.

Running computer-use evaluations at scale

Cua Bench defines verifiable tasks with evaluators, and the same tasks can run locally or on disposable desktops in your own cloud account, so many rollouts run in parallel on identical images.

Delegating signed-in desktop work to an agent you can watch

Cua Spaces gives the agent its own desktop with a teleported, signed-in app session, streams it live, and lets you take the cursor for a decision before handing it back.

How Cua fits alongside other tools

Cua and Claude Code

Claude Code is the agent: it plans, writes code, and calls tools. Cua Driver is one of those tools, registered as an MCP server, that lets Claude Code operate native apps, and the Cua SDK can run Claude Code inside a sandboxed desktop. Use them together when a coding task needs a GUI step, such as QA on a desktop app.

Cua and Hermes Agent

Hermes Agent is Nous Research's self-hosted autonomous agent, and Cua Driver is the engine behind its built-in computer_use toolset. Enabling that toolset in Hermes gives the agent Cua's background desktop control, so you do not register Cua Driver as a separate MCP server.

Cua and Browser Use

Browser Use automates websites through a browser agent library and cloud browsers. Cua controls whole desktops, including native apps, with browser tabs as one surface among many. A team can keep Browser Use for web-only flows and add Cua for steps that leave the browser, such as native apps or file dialogs.

Cua and DigitalOcean Managed Agents

DigitalOcean Managed Agents hosts agents such as Claude Code or Codex in microVMs with a governed tool gateway. Cua supplies GUI desktops, a desktop driver, and eval tooling. A team could host its agent on one and give it computers through the other.

Frequently asked questions

What is Cua?

Cua is open-core infrastructure for computer-use agents, made by Cua AI, Inc., a Y Combinator (X25) company. It includes Cua Driver for letting agents operate native apps on macOS, Windows, and Linux, the Cua SDK and CLI for local and cloud sandboxes, the Cua Spaces app for working alongside agents on shared desktops, Lume for Apple silicon VMs, and Cua Bench for evaluating agents.

Is Cua open source?

Mostly. Everything in the trycua/cua repository outside Cua Spaces and Cua Driver Bench is MIT-licensed, including Cua Driver, the SDKs, the cua CLI, Lume, and Cua Bench. Cua Spaces (the apps, cua-spacesd, the Keyvault, Teleport, Cua Volume, and the streaming client) is source-available under FSL-1.1-MIT, as is Cua Driver Bench from October 11, 2026: free to use, self-host, and build on, except as a competing hosted service, and each release becomes MIT two years after it ships.

How much does Cua cost?

The open-source components are free. Cua Spaces is free for up to 2 live sessions and 20 remote hours a month; Pro costs $18 a month ($15 a month billed yearly) for 5 live sessions and 200 remote hours, and Teams costs $30 per seat a month ($25 billed yearly), with each seat adding 5 sessions and 200 hours to a shared pool. Remote hours count only time spent through Cua's relay, and nothing is cut off if you go over. Cua does not host computers, so sandboxes run on your own machines or in your own AWS, Google Cloud, Hetzner, or Modal account, billed by that provider.

Does Cua still offer a hosted cloud?

No. Cua Cloud and Fleets, including managed pools, warm replicas, and the Terraform provider, ended on October 18, 2026. Cua points users to local sandboxes, their own AWS, Google Cloud, or Modal account (Hetzner is also supported), or machines connected through Cua Spaces.

Which agents and models work with Cua?

Cua Driver connects to Claude Code, Codex, Cursor, Antigravity CLI, OpenClaw, Hermes, OpenCode, Factory Droid, Qwen Code, Kimi Code, Pi, and any MCP client, and the Cua SDK can run Claude Code, Codex, Gemini CLI, OpenCode, and Goose inside a sandbox. The harness supplies the model, so Claude, OpenAI, Gemini, Kimi, and Qwen models work through their own agents, and local models can run through Ollama or llama.cpp.

Which operating systems does Cua support?

Cua Driver supports macOS 14 or later, Windows 10 and 11 or Server, and Linux on X11 and some Wayland compositors with limits. The SDK can create Linux, Windows, and macOS desktops locally, and Linux desktops in your own cloud account. The Cua Spaces app runs on macOS 26 or later, Ubuntu 24.04, and Windows in preview, and macOS Spaces need Apple silicon.

Is Cua Spaces safe to use with my signed-in apps?

Teleport shows a consent screen for every install, file, and state item, needs an explicit acknowledgement for secrets, and on macOS asks for Touch ID or your password before cookies are read. On Space images the bundle is sealed end to end to that Space's key. Current Spaces apps, the CLI, and cua-spacesd connect over an end-to-end encrypted mesh by default, so the relay cannot read the stream, input, or files, but browser viewers, share links, older versions, and fallback connections use a relay path that can; setting CUA_MESH=require blocks that path. Anyone who controls the destination Space can use a teleported session, so teleport only into Spaces you control.

Integrations & fit

Claude CodeOpenAI CodexCursorAntigravity CLIOpenClawHermesOpenCodeFactory DroidQwen CodeKimi CodePiGemini CLIGooseClaude Agent SDKCodex SDKMCPOllamallama.cppDockerPodmanQEMUAWSGoogle CloudModalE2BDaytonaHetznerGitHub ActionsTailscale
Good fit forSolo / individual, Startup / small team, Enterprise
Pricing modelFreemium· Free tier available
See pricing on Cua →

About Cua

Cua does not ship its own agent. It supplies the computer and the hands, and you bring the agent and the model. The core piece is Cua Driver, an MIT-licensed binary that reads each window's accessibility tree and screenshot and then clicks, types, scrolls, and drives browser tabs, in the background where the operating system allows it, so the person at the keyboard keeps their cursor and focus while the agent gets its own cursor overlay. Agents reach it as an MCP server, through a CLI, or through Python and TypeScript SDKs, and the docs give setup for Claude Code, Codex, Cursor, Antigravity, OpenClaw, Hermes, OpenCode, Factory Droid, Qwen Code, Kimi Code, and Pi; the harness owns the model and the loop, and Cua Driver never calls a model API. When an agent should not touch your own machine, the Cua SDK and `cua` CLI create disposable Linux, Windows, and macOS desktops locally (Docker or Podman, QEMU, Lume, or Hyper-V), on any machine running Cua's guest daemon, through E2B or Daytona, or in your own AWS, Google Cloud, Hetzner, or Modal account. Cua no longer hosts machines itself: Cua Cloud and its Fleets pools ended on October 18, 2026. Cua Spaces, first released at the start of October 2026, is an app for macOS, Linux, and Windows (in preview) that lists those desktops, streams them live, gives you and each agent a separate cursor on the same desktop so you can step in and hand it back, and can teleport a signed-in app session such as Chrome or Slack into a Space after you approve each item. It is free for up to 2 live sessions and 20 remote hours a month, and the Pro ($18 a month) and Teams ($30 per seat a month) plans add sessions, hours, and shared team computers. Lume manages macOS and Linux VMs on Apple silicon, and Cua Bench runs verifiable desktop tasks and adapters for benchmarks such as OSWorld-Verified and WebVoyager. The tradeoffs: this is developer infrastructure rather than a finished assistant, so you need an agent harness and model credentials of your own, and you also supply the machines, with Windows and macOS not offered in your own cloud account; Cua Spaces is source-available under FSL-1.1-MIT rather than MIT, and the Mac app needs macOS 26; driver coverage on Linux depends on the toolkit and compositor; and while current Spaces versions encrypt sessions end to end by default, browser viewers, share links, and older versions still go through a relay path that can read them.

Updates from Cua

New FeatureCua Spaces 0.13 to 0.16

Cua Spaces 0.13 through 0.16, summarized in Cua's October 25 changelog, start onboarding with your agents and add E2B, Daytona, Hetzner, and a shared pool of computers as places to run Spaces. From Spaces 0.13.0, CLI and SDK 0.7.0, and cua-spacesd 0.7.0, connections use an end-to-end encrypted mesh by default, so the relay can no longer read the desktop stream, input, or files on those connections.

UpdateCua Cloud and Fleets end

Cua shut down Cua Cloud and Fleets, including managed pools, claims, warm replicas, and the Terraform provider. Cua now points users to local sandboxes, their own AWS, Google Cloud, or Modal account, or machines connected through Cua Spaces, and marked cuabot, cua-computer, cua-computer-server, and cua-agent as unmaintained.

New FeatureCua Spaces 0.9 brings the new UI and a Teams screen

Cua Spaces 0.9.0 made the redesigned app, the same UI as the new Windows and Linux app, the default and added a Teams screen listing organizations, members, and invites, plus dragging windows or files onto a Space to teleport or send them.

LaunchCua Spaces released

Cua released Cua Spaces, a free Mac app that gives agents their own desktops on your Mac, on machines you own, or in your own cloud, with live streaming, separate cursors for you and each agent, and Teleport for moving signed-in app sessions into a Space after approval. Version 0.1.0 was published on GitHub on October 1, 2026. Spaces is source-available under FSL-1.1-MIT, and Pro and Teams plans are on a waitlist.

New FeatureBrowser control without a Chrome extension

Cua Driver now binds an exact Chromium tab to its native process and window, giving agents page-aware browser actions and full desktop control in the same session without installing a browser extension.

New FeatureCua Driver adds Linux background computer use

Cua Driver began driving Linux desktop apps in the background, using AT-SPI 2 for the accessibility tree, XTEST for input, and a painted agent cursor separate from the user's pointer on X11 and XWayland.

New FeatureCua Driver adds Windows background computer use

Cua Driver gained Windows support across Win32, WPF, WinUI, UWP, Electron, and legacy controls, with synthetic cursors so agents can work in background windows.

Are you the founder? Claim this listing →