Individual skill

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

skills/ops-and-setup/cua-driver/SKILL.md

Read pinned source

Source commit 8aa01cf45110ae378bdf5c319cd41ac8fdbdf448

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Network or broad shell
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 4,287
Repository last updated: Nov 9, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

design Derived category
testing Derived category
productivity Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,293 bytes
SKILL.mdcore · 3,293 bytes
references/capabilities.mddoc · 3,393 bytes
references/setup.mddoc · 3,117 bytes

Read excerpt


# Cua Driver

Cua Driver is an MIT-licensed local automation tool, not a model. Pi or another
agent supplies the reasoning; the driver reads accessibility trees/screenshots
and sends input to apps. No Cua cloud account or VM is needed. Host control is
not sandboxed, and desktop content sent to a cloud model leaves the machine.

## Before acting

```bash
command -v cua-driver
cua-driver --version
cua-driver status
cua-driver permissions status --json