feat(cua-driver): vendor qwen-cua-driver with opt-in 0–1000 relative coordinates

packages/cua-driver/.gitignore

@@ -0,0 +1,9 @@
+# Vendored fork of trycua/cua → libs/cua-driver.
+#
+# Upstream relied on the cua monorepo root .gitignore to ignore Rust build
+# output (`target/`). That root is gone in this vendored copy, so re-declare
+# the generated artifacts here to keep `cargo build` output out of git.
+target/
+*.pyc
+__pycache__/
+.DS_Store

packages/cua-driver/.vendored-from

@@ -0,0 +1 @@
+cua-driver-rs-v0.6.8

packages/cua-driver/README.md

@@ -0,0 +1,23 @@
+# Cua Driver
+
+Background computer-use driver for any agents. Speaks MCP over stdio; drives native macOS apps without stealing focus.
+
+**[Documentation](https://cua.ai/docs/cua-driver)** - Installation, guides, and API reference.
+
+## Claude Code computer-use compatibility
+
+Standard Claude Code MCP registration:
+
+```bash
+claude mcp add --transport stdio cua-driver -- qwen-cua-driver mcp
+```
+
+If you want Claude Code's vision/computer-use-style flow to ground on QwenCuaDriver window screenshots, register the compatibility mode:
+
+```bash
+claude mcp add --transport stdio cua-computer-use -- qwen-cua-driver mcp --claude-code-computer-use-compat
+```
+
+This keeps QwenCuaDriver's normal MCP tools and changes only `screenshot`, which requires `pid` and `window_id` and captures that window only.
+
+Use MCP for this Claude Code vision/computer-use-style path. CLI screenshots still work as QwenCuaDriver calls, but they do not expose the `mcp__cua-computer-use__screenshot` tool name that Claude Code appears to use as the image-grounding cue.

packages/cua-driver/docs/tool-output-format.md

@@ -0,0 +1,39 @@
+# cua-driver MCP Tool Output Format
+
+Every tool call returns a ✅ checkmark + concise summary. No structured JSON output.
+
+## screenshot
+```
+✅ Screenshot — 1920x1080 png
+
+On-screen windows:
+- Terminal (pid 7476) "cua — Claude Code" [window_id: 2102]
+- Blender (pid 6808) "* Untitled - Blender 5.1.1" [window_id: 2129]
+- Google Chrome (pid 13313) "Download — Blender" [window_id: 1941]
+→ Call get_window_state(pid, window_id) to inspect a window's UI.
+```
+
+## get_window_state
+```
+✅ Blender — 11 elements, turn 3 + screenshot
+⚠️  Small AX tree (11 elements) — this app likely uses custom rendering
+    (e.g. Blender, games, Electron). Use pixel clicks: click(pid, x, y)
+    with coordinates from the screenshot.
+
+- AXApplication "Blender"
+  - [0] AXWindow "* Untitled - Blender 5.1.1" actions=[AXRaise]
+    - [1] AXButton
+    ...
+```
+
+## click
+```
+✅ Posted click to pid 6808.
+```
+
+## zoom
+```
+✅ Zoomed region captured at native resolution. To click a target in
+this image, use `click(pid, x, y, from_zoom=true)` where x,y are pixel
+coordinates in THIS zoomed image — the driver maps them back automatically.
+```

packages/cua-driver/python/.gitignore

@@ -0,0 +1,16 @@
+# Build artifacts
+dist/
+build/
+*.egg-info/
+__pycache__/
+*.pyc
+*.pyo
+
+# Downloaded binaries and archives
+downloads/
+src/cua_driver/bin/
+
+# Virtual environments
+venv/
+.venv/
+env/

packages/cua-driver/python/MANIFEST.in

@@ -0,0 +1,2 @@
+include README.md
+recursive-include src/cua_driver/bin *

packages/cua-driver/python/README.md

@@ -0,0 +1,74 @@
+# cua-driver
+
+Python wrapper for [cua-driver](https://github.com/trycua/cua/tree/main/libs/cua-driver) - a cross-platform MCP (Model Context Protocol) server for computer-use automation.
+
+## Installation
+
+```bash
+pip install cua-driver
+```
+
+## Usage
+
+The package provides a `cua-driver` command that wraps the native Rust binary:
+
+```bash
+# Start MCP server over stdio
+cua-driver mcp
+
+# Check version
+cua-driver --version
+
+# View help
+cua-driver --help
+```
+
+### Python API
+
+You can also use the Python API directly:
+
+```python
+from cua_driver import run_cua_driver, get_binary_path
+
+# Run with custom args
+exit_code = run_cua_driver(["mcp"])
+
+# Get path to bundled binary
+binary_path = get_binary_path()
+```
+
+## Features
+
+- **Cross-platform**: Works on macOS (universal), Linux (x86_64), and Windows (x86_64/ARM64)
+- **Zero dependencies**: Pure Python wrapper with no external dependencies
+- **Stdio passthrough**: Transparent piping for MCP protocol communication
+- **Bundled binary**: No separate installation required - the Rust binary is included in the wheel
+
+## What is cua-driver?
+
+`cua-driver` is a cross-platform MCP server that provides 40+ tools for:
+- Screen capture and window management
+- Mouse and keyboard automation
+- Accessibility tree interaction
+- Application launching and control
+
+It enables AI agents to interact with desktop applications through the Model Context Protocol.
+
+## Platform Support
+
+| Platform | Architecture | Status |
+|----------|-------------|---------|
+| macOS    | Universal (ARM64 + x86_64) | ✅ Supported |
+| Linux    | x86_64 | ✅ Supported |
+| Windows  | x86_64 | ✅ Supported |
+| Windows  | ARM64 | ✅ Supported |
+
+## License
+
+MIT License - see [LICENSE](https://github.com/trycua/cua/blob/main/LICENSE.md)
+
+## Links
+
+- [GitHub Repository](https://github.com/trycua/cua)
+- [Documentation](https://github.com/trycua/cua/tree/main/libs/cua-driver)
+- [Issue Tracker](https://github.com/trycua/cua/issues)