What our run establishes
In our run on 2026-09-27 at commit e1c44bd, the harness recorded a successful 14-second root install. Build and test were skipped because the detected root scripts contained neither target. The matching raw record also detected a tests directory and Python tests, so the skipped root test step does not establish that Cua lacks tests.
The sandbox used the lab-node:22 image with 3 CPUs and 8 GB of memory. Our harness records each step separately, including success, elapsed time, exit code, timeout status, and skip reason where present. The root install returned exit code 0 without timing out. We did not test Driver actions, VM startup, cloud provisioning, model inference, or agent task completion.
The stored dependency summary reports 2 packages and 9 MB, while the retained command tail reports one package added and its own shorter duration. We have not reconciled those observations against a complete log. The stored checkout measurements are 5,266 files, 959,948 source lines, and 320 MB; they describe repository size, not installed product coverage. The audit result is null, so this run supplies neither an advisory result nor known scan coverage.
The MrKeyoor testing methodology explains how command results reach our reviews. It is provenance context, not evidence that its current procedure was used unchanged for this older run.
Pick the component that answers your task
Cua Driver provides tools to inspect and operate native desktop apps and browsers on macOS, Windows, and Linux. It connects through a CLI, MCP, or typed SDKs. Bring your own agent and model; Cua's documented role is to supply computers and automation tools.
Lume manages local macOS and Linux VMs on Apple Silicon. Cua Bench builds evaluation tasks and exports trajectories. Its documented simulated starting task requires no VM, Docker, or model API key. These are separate entry points, so completing a root package install does not validate any of them.
The README at our measured commit presents Cua Fleets for isolated cloud desktops. The current README instead leads with Cua Spaces and also documents the SDK and CLI. Current Spaces requirements and licensing should therefore guide a current evaluation, without being attributed to our September run.
Check background control against your actual platform
The current Driver platform reference makes support conditional on the application and delivery route. macOS needs Accessibility and Screen Recording permissions. Windows elevated targets can refuse input. Linux support depends on the display session, compositor, and application backend.
For Wayland, the reference distinguishes Sway coverage from experimental KDE and Hyprland routes. Semantic background actions can work where applications expose them, while raw input to an occluded window generally cannot. A broad operating-system label is insufficient to choose a deployment target.
Use the documented Calculator exercise as a first check: ask the agent to compute 6 × 7 and verify that Calculator displays 42. That is a proposed next step from the README, not an exercise completed in our sandbox. Follow it with a representative task in your own application, including the background behavior you need.
Compare the layer you need
Browser Use offers a Python library for running its browser agent locally with a choice of model and a local or cloud browser. Consider it when the task stays in a browser and you want that agent layer. Cua Driver instead supplies desktop controls to an agent you bring. The two may serve different parts of a system; browser automation alone does not establish native desktop coverage.
E2B supplies cloud sandboxes for AI-generated code and a separate Desktop SDK for mouse, keyboard, screenshots, applications, and desktop streaming. Consider E2B when evaluating cloud execution or desktop infrastructure. It overlaps with Cua's sandbox and desktop needs, so dismissing it as code execution alone would miss a documented capability. These alternatives were not installed or compared in our run.
Check the current component license
The current README places the SDK, CLI, Driver, and Lume under MIT unless a directory states otherwise. Spaces components and Cua Driver Bench use FSL-1.1-MIT, with restrictions on competing hosted services and conversion of each release to MIT after two years. Optional perception artifacts carry additional terms. Check the exact component and artifact you intend to ship; the root license signal in our stored record is insufficient for that decision.
How to read our ratings
These are editorial ratings, not benchmark results. Setup ease uses 1 for a blocked install, 2 for an install that leaves product setup unverified, 3 for a verified component setup, 4 for a documented repeatable setup, and 5 for verified setup across the evaluated targets. Cua receives 2 because our root install completed while product setup remained untested.
Documentation uses 1 for missing entry instructions, 2 for basic installation notes, 3 for component quickstarts, 4 for quickstarts plus platform requirements, and 5 for those materials plus explicit support boundaries and licensing guidance. The supplied current README and platform reference meet the fifth category; this does not mean we executed their instructions.
Community uses 1 for no documented participation route, 2 for one route, 3 for multiple routes, 4 for those routes plus contribution guidance, and 5 for all of those plus private security reporting. The supplied README meets the fifth category through its Discord, issues, contribution, and security links. This rates the documented participation routes, not adoption, responsiveness, or user satisfaction.
Maturity uses 1 for a concept without a usable path, 2 for an early implementation, 3 for documented usable paths with material experimental boundaries, 4 for demonstrated coverage across the evaluated scope, and 5 for that coverage plus operational validation. Cua receives 3 because the current documentation describes usable paths alongside experimental routes and open evidence gaps. Our run provides no production validation.

