[中文](README.md) · English

# dsh-cua-drive

macOS only. After install, the in-host agent uses a private, lock-pinned [`cua-driver`](https://github.com/trycua/cua) **0.20.0** (`runtime-lock.json`) to click windows, read the screen, and drive apps. It runs on this plugin's own socket and does not stop, change, or hijack a Cua install already on the machine.

First launch asks the process that started dsh for Accessibility and Screen Recording. DSH.app: grant **DSH**. CLI `dsh web`: grant Terminal / iTerm / Cursor / VS Code. Windows and Linux only load `cua_status` and say this is macOS-only. They do not download a driver or start computer-use.

The package name is `dsh-cua-drive`. The repo is still `dsh-cuadrive-mac`, so existing downloads, permissions, sockets, and sessions do not move.

## Install

Pin a commit, restart DSH, open a new chat. The repo ships built `lib/`. A GitHub install does not run `prepare`.

```sh
dsh plugin --profile web add github:aa2246740/dsh-cuadrive-mac#593da95209f755a9bfa43ab002c504f67f07c2cd
```

The first Mac start needs network once, to pull the pinned darwin-universal tarball into `$DSH_HOME/dsh-cuadrive-mac/vendor/`. If that fails, set `HTTPS_PROXY` / `ALL_PROXY` / plugin config `proxy`, or drop the same tarball at `runtime.manualCachePath`. Do not run `cua-driver update`.

Upgrading from an old `my-plugins` install: delete the `dsh-cuadrive-mac` row from `cordis.patch.yml` first. The bundle now owns the Loader. Two copies fail boot with a duplicate id.

## First launch on a Mac

| How you run dsh | Grant in System Settings |
|---|---|
| DSH.app | DSH |
| CLI `dsh web` with no app pack | Terminal / iTerm / Cursor / VS Code, the parent app |

Do not run `cua-driver permissions grant`. That pulls `/Applications/CuaDriver.app`. Grant the name in `cua_status.hostPermissions.hostLabel`.

Progress is the `cua_status` card title, or `$DSH_HOME/dsh-cuadrive-mac/status.json` and `download.log`.

Windows / Linux only load the status tool:

![Linux cua_status: supports macOS only](docs/screenshots/linux-cua-status.png)

Private runtime lives under `$DSH_HOME/dsh-cuadrive-mac/`. Closing DSH stops only `run/driver.sock`. Tools exposed to the model stay named `cua_*`.

## Config

| key | default | meaning |
|---|---|---|
| `binary` | empty | Absolute override. Empty uses the plugin vendor dir |
| `ownDaemon` | `true` | Private DSH socket |
| `socketPath` | `$DSH_HOME/dsh-cuadrive-mac/run/driver.sock` | Serve for DSH only |
| `autoStart` | `true` | Download and `serve --embedded` if the socket is down |
| `proxy` | empty | HTTP(S) proxy for GitHub downloads |
| `promptPermissions` | `true` | Ask the host that launched dsh on first use |
| `timeoutMs` | `90000` | Per-call timeout |
| `sessionId` | `dsh` | Hosted session on the private daemon |

## Local development

Clone outside the Harness repo, then in this directory:

```sh
npm ci
npm test
npm run typecheck
npm run build
dsh plugin --profile web add .
```

MIT.