Skip to content
Tech News
← Back to articles

Show HN: CUA-S1 – A System One Model for Computer Use

read original more articles
Why This Matters

This Show HN post introduces CUA-S1 and related tooling (Cua Fleets, Cua Driver) that let AI agents directly control desktop apps, browsers, and cloud sandboxes across macOS, Windows, and Linux, bridging code, APIs, and GUIs in a single task. It matters because it pushes 'computer use' agents beyond simple browser automation toward general-purpose desktop control, a key step toward more capable autonomous AI assistants.

Key Takeaways

Choose your path

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.

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, then explore Omarchy on Fleet.

recording.mp4

Cua Fleets

Provision isolated cloud desktops at run.cua.ai. A Fleet maintains sandbox capacity; your code claims a desktop from a pool and uses the Sandbox SDK to run commands, capture screenshots, and interact with apps inside it.

Your first result: provision a Linux desktop, run uname -a , save a screenshot, and delete the cloud resources. The tutorial covers Fleet credentials, dependencies, and cleanup. Pools can retain paid capacity after a claim ends, so follow its cleanup steps.

Local sandboxes and Fleets share the Sandbox SDK, but credentials, images, operations, and runtime requirements differ. Use the runtime support reference to choose an environment. For your own hardware, see Manage local sandbox lifecycle.

Your first Cloud Fleet | Fleet overview | Sandbox SDK reference

... continue reading