Cua

Give AI agents computers they can use.
Cua Spaces gives your agents full desktops on your Mac and on machines you own. This repository also holds Cua Driver for desktop automation, Lume for local VMs, CUA-S1 decision models and Cua Bench for evaluating computer-use agents.

Get Cua Spaces

<a href="https://discord.gg/mVnXXpdE85" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Discord-Join%20Server-10b981?logo=discord&logoColor=white" alt="Discord"></a>
<a href="https://x.com/trycua" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/twitter/follow/trycua?style=social" alt="Twitter"></a>
<a href="https://cua.ai/docs" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Docs-0ea5e9.svg" alt="Documentation"></a>
<br>

Choose your path

• Cua Spaces: Install the app and run your first Space.
• Cua Driver: Operate Calculator and verify its result.
• Lume: Create a Tahoe VM and connect over SSH.
• Cua SDK and CLI: Install cua and create a local sandbox.
• CUA-S1: Explore small, specialized models for computer-use decisions.
• Cua Bench: Create and verify a simulated task.

Bring your own agent and model, or explore CUA-S1 for specialized decisions. Cua provides the computer and automation tools. Computer-Use 2.0 describes an agent moving between code, APIs, and graphical interfaces within the same task.

Cua Spaces

Cua Spaces is a desktop app that gives your agents full desktops. Each desktop is a Space: a macOS VM built locally on your Mac, or a Linux or Omarchy image. Spaces run on your Mac, on other machines you own, and in your own cloud account (AWS, Google Cloud or Modal), and the app keeps them in your menu bar and notch.

• Teleport. Move a signed-in app, such as Chrome or Slack, into a Space and it opens there still signed in. Your sessions stay in the Cua Keyvault, encrypted on your Mac, and reach a Space only after you approve.
• Multiplayer. You and your agents work on the same desktop, each with your own cursor. Step in to make a choice, then hand the desktop back.
• Agent-ready images. Spaces images ship with cua-spacesd, so agents get processes, files, screenshots and input as soon as a Space starts.

https://github.com/user-attachments/assets/a2ccc86b-10d0-48c0-bee6-7ae652ba1c59

Install on macOS 26 or later

curl -fsSL https://cua.ai/install.sh | sh

On macOS the installer selects the Cua Spaces app by default and adds the cua CLI. You can also download the signed .dmg, or get the .pkg from the Cua Spaces 0.9.4 release.

Spaces is free for individuals. Pro is $18 a month and Teams is $30 per seat a month, available now from 1 seat. See pricing. The app is source-available under FSL-1.1-MIT.

Quickstart | Teleport an app | Share a Space | Host Spaces on a spare Mac (relay, Tailscale or SSH) | Your own cloud | App source

Cua Driver

Give your agent tools to inspect and operate native desktop apps and browsers on macOS, Windows, and Linux. Connect through the CLI, MCP, or typed SDKs. Background delivery lets agents work without moving your pointer or taking focus when the app and platform support it; see platform support for the boundaries.

macOS / Linux

/bin/bash -c "$(curl -fsSL https://cua.ai/driver/install.sh)"

Windows (PowerShell)

irm https://cua.ai/driver/install.ps1 | iex

Your first result: connect your agent, ask it to compute 6 × 7 in Calculator, and have it verify that the app displays 42. The tutorial covers platform setup, permissions, and agent connection.

Drive your first app | Installation | CLI Reference

Using Claude Code, Codex, Cursor, OpenClaw, or another agent? Find your integration. Source documentation and architecture notes live in libs/cua-driver/README.md.

See Cua Driver in action

Two Cua Driver sessions select cells in LibreOffice Calc and objects in Inkscape on an Omarchy desktop while a terminal stays in the foreground. Watch the 50-second demo.

https://github.com/user-attachments/assets/b4e5517c-d2db-4758-b4cf-07131b0753b2

Lume

Create and manage local macOS and Linux VMs on Apple Silicon using Apple's Virtualization.Framework.

/bin/bash -c "$(curl -fsSL https://cua.ai/lume/install.sh)"

Your first result: create a vanilla macOS Tahoe VM from an Apple restore image, start it, and connect over SSH. The tutorial uses the Lume CLI directly and explains the unattended setup defaults.

Create your first Lume VM | Installation | CLI reference

Cua SDK and CLI

One SDK and one cua command for local VMs and containers, and for any machine that runs cua-spacesd.

macOS / Linux

curl -fsSL https://cua.ai/install.sh | sh

Windows (PowerShell)

irm https://cua.ai/install.ps1 | iex

In a terminal the script first says what Cua Spaces is. The command-line tools (the cua program) are always installed; you choose whether to add the Cua Spaces app (on by default) and Cua Driver, which lets AI agents use your apps while you keep working (off by default). It then runs cua auth login, which signs you in and offers to set up your AI coding agents (Claude Code, Codex, Cursor, and others). The app asks on its first run whether your other devices may use this computer. Add Cua Driver with sh -s -- --select cua-driver, or skip the choice with --only cua-driver. See the installer options.

cua sb create ubuntu --name dev          # a gVisor container, set up on first use
cua sb exec dev uname -a
cua sb screenshot dev
cua sb rm dev

The same sandbox from Python:

from cua_sandbox import Image, Sandbox

async with Sandbox.ephemeral(Image.linux(), local=True) as sb:
    print((await sb.shell.run("uname -a")).stdout)

• SDK: the same API in Python (pip install cua), TypeScript (@trycua/cua) and Rust (cua-sdk), running embedded in your process or through a shared cua daemon. Swift and Kotlin bindings are not yet released.
• Sandboxes need no agent inside. Readiness comes from the runtime and optional port probes. Images that ship cua-spacesd (port 3211) add processes, files, screenshots, input through cua-driver, and low-latency video and audio streaming. There is no agent layer in the SDK either: drive sandboxes from your own harness (guide).
• Your own machines. cua host setup makes this machine reachable through the cua.ai relay with no port forwarding.

SDK README | Quickstart | CLI reference | Sandbox SDK reference

CUA-S1

CUA-S1 is our family of small, specialized System 1 models for computer use. We use "System 1" as an engineering analogy for fast, bounded decisions, such as choosing which value belongs in a field or whether to leave an element alone. It is not a strict classification of model architectures or a replacement for a general-purpose agent's planning and reasoning.

The first research profile focuses on forms: scoring decisions from structured interface elements and document values rather than generating a response token by token. Application code orders the actions, and the optional Cua Driver integration handles execution with explicit action boundaries.

The project includes Python model code, synthetic-data generation, training, and evaluation. The GitHub component is an early, source-only research release; model weights are hosted separately on Hugging Face. The source is MIT-licensed. Check each model and dataset card for its scope, limitations, and artifact-specific license.

Explore CUA-S1 | Model card | Safety and deployment guidance

CUA-S1-FORMS on Hugging Face: Model weights | Dataset

Cua Bench

Build computer-use tasks, evaluate agents, and export trajectories for training. Start with a simulated task that requires no VM, Docker, or model API key.

With Python 3.12 or 3.13 and uv installed:

uv tool install 'cua-bench[browser]'
uv tool run --from 'cua-bench[browser]' playwright install chromium

Your first result: create a small task, run its reference solution, and verify that its evaluator reports a reward of 1.0. Then try the same task yourself.

Build your first task | What is Cua-Bench? | CLI reference | Partner with us

Packages

Deprecated packages

Cua no longer maintains these. They will not receive updates or fixes, and existing releases stay on npm and PyPI. See Migrate from deprecated packages.

Resources

• Documentation: guides, examples, and API reference
• Blog: tutorials, updates, and research
• Discord: community support and discussions
• GitHub Issues: bug reports and feature requests
• Security: private vulnerability reporting

Citation

If Cua supports your research, please cite the software:

@software{cua2025,
  author  = {{Cua AI, Inc.}},
  title   = {Cua},
  year    = {2025},
  url     = {https://github.com/trycua/cua},
  license = {MIT}
}

For reproducibility, include the Cua release or commit used in your experiments. Citation metadata is also available in CITATION.cff.

Contributing

We welcome contributions. See our Contributing Guidelines for details.

Licensing

Everything outside Cua Spaces and Cua Driver Bench is MIT-licensed (LICENSE): the cua SDK and its Python, TypeScript, Swift and Kotlin packages, the cua command and cua daemon, Cua Driver, Lume and the rest of this repository unless a directory says otherwise. Cua Spaces is source-available under FSL-1.1-MIT: the Spaces apps, cua-spacesd, the Cua Keyvault, teleport, Cua Volume (cua-volume) and the streaming client, codecs and viewers. The streaming wire protocol stays MIT. It is free to use, self-host and build on, with no competing hosted service, and each release becomes MIT two years after it ships. Cua Driver Bench (libs/cua-driver-bench) is under the same FSL-1.1-MIT; versions published before 11 Oct 2026 (#4973, #4978) were MIT. The MIT parts never depend on the FSL parts. Some subdirectories carry their own licence; LICENSING.md lists each one and how the two fit together. Offering Spaces, or Cua Driver Bench, as a hosted or managed service? See COMMERCIAL.md. For use of our names and logo, see TRADEMARKS.md.

Third-party components have their own licenses:

• Kasm (MIT)
• [cua-som](https://github.co