qwenpaw/plugins/bundle/computer-use/README.md

# Computer Use

Computer Use is a desktop plugin backed by the QwenPaw desktop host, supported
on Windows and macOS. The Python plugin contains only the tool adapter,
approval bridge, and usage skill. Window discovery, screen capture,
accessibility inspection, input injection, and target validation run in the
host-managed native helper.

The helper is not installed from this directory. It is packaged with the
desktop application and receives a short-lived private transport capability
from the host (a named pipe on Windows, a Unix domain socket on macOS).

## Layout

```text
computer-use/
|- plugin.py                    Plugin registration
|- computer_use/                Protocol adapter and approval bridge
|- frontend/                    Console UI sources (approval card, settings)
|- dist/index.js                Built console UI bundle (committed artifact)
`- skills/computer_use/         Tool operating guidance
```

The plugin has no Python GUI automation dependencies.

Its tests live in `tests/unit/plugins/computer_use/` rather than here, so the
standard `pytest tests/unit` suite collects them: pytest ignores `testpaths`
whenever a path is passed on the command line, and a suite inside the plugin
directory would therefore never run.

## Console UI

The manifest points `entry.frontend` at `dist/index.js`. That bundle is a build
artifact of `frontend/`, and it is committed rather than gitignored so the
plugin installs on a machine with no npm toolchain -- the same arrangement
`plugins/bundle/qwenpaw-pet` uses, and the reason the repository `.gitignore`
carries an exception for this path.

It therefore has to be rebuilt and committed alongside any edit under
`frontend/src/`, or the console keeps running the previous UI:

```bash
cd frontend && npm install && npm run build
```


## Native helper

The helper is a Rust binary in `console/src-tauri/src/computer_use_server/`,
with a leaf directory per platform. Windows builds and tests locally:

```bash
cd console/src-tauri && cargo test --bin qwenpaw-computer-use-helper
```

A change under `platform_macos/` needs a macOS compiler, so verify it with the
desktop verification workflow, which can build that platform on its own:

```bash
gh workflow run fork-verify-desktop.yml -f platforms=macos-only
```

Worth actually running rather than reasoning about: static checks can confirm a
symbol exists, not that a type, a lifetime or a trait bound holds.