Skip to content

Computer use for the Pi coding agent — Windows apps, browsers and desktops through native UI trees, screenshots and real input.

Docs: runtime 33c4b82b and the resize size difference (LPT-940)

alexshpunt-clanker[bot]2772a0c241be
diff --git a/docs/bundled-runtime.md b/docs/bundled-runtime.md
index 43736d9..b3b207b 100644
--- a/docs/bundled-runtime.md
+++ b/docs/bundled-runtime.md
@@ -1,6 +1,6 @@
# Bundled CUA runtime
-The npm package carries one native runtime: Cua Driver 0.37.0 for Windows x64, built from the `pi-computer-use` branch of the [alexshpunt/cua](https://github.com/alexshpunt/cua) fork at source `e2c256de`. [FORK.md](https://github.com/alexshpunt/cua/blob/pi-computer-use/FORK.md) lists what the fork adds to upstream Cua Driver. It is the qualified `windows-desktop` profile, so a fresh installation gets every native capability without any configuration:
+The npm package carries one native runtime: Cua Driver 0.37.0 for Windows x64, built from the `pi-computer-use` branch of the [alexshpunt/cua](https://github.com/alexshpunt/cua) fork at source `33c4b82b`. [FORK.md](https://github.com/alexshpunt/cua/blob/pi-computer-use/FORK.md) lists what the fork adds to upstream Cua Driver. It is the qualified `windows-desktop` profile, so a fresh installation gets every native capability without any configuration:
```sh
pi install npm:pi-agent-computer-use
@@ -10,7 +10,7 @@ An update installs a new extension version with its exact runtime. Computer use
## Where the files come from
-The files are published as the fork release [`pi-runtime-0.37.0-e2c256de`](https://github.com/alexshpunt/cua/releases/tag/pi-runtime-0.37.0-e2c256de): `cua-driver.exe`, `cua-driver-uia.exe`, `cua-cursor-theme.exe`, `LICENSE.md` and `THIRD_PARTY_NOTICES.md`. They are byte-identical to the fork's CI build of that commit.
+The files are published as the fork release [`pi-runtime-0.37.0-33c4b82b`](https://github.com/alexshpunt/cua/releases/tag/pi-runtime-0.37.0-33c4b82b): `cua-driver.exe`, `cua-driver-uia.exe`, `cua-cursor-theme.exe`, `LICENSE.md` and `THIRD_PARTY_NOTICES.md`. They are byte-identical to the fork's CI build of that commit.
`src/runtime-pins.json` pins the source, the version, the release URL and the SHA-256 of every file. Before packing, `npm pack` runs `scripts/fetch-runtime.mjs`, which downloads the files into `native-runtime/win32-x64/runtime/` and checks each hash. The directory is not committed to Git.
diff --git a/docs/computer-resources.md b/docs/computer-resources.md
index 3b48f76..9b6f54d 100644
--- a/docs/computer-resources.md
+++ b/docs/computer-resources.md
@@ -158,7 +158,7 @@ An `aria` template is Playwright's YAML, such as `- list "Pick":\n - listitem "
### Windows and displays
-`computer_window` samples the window's state and sends one command. Move and resize take integer Windows desktop pixels, not image, CSS or DIP coordinates, and need a normal window that is neither minimized nor maximized. Maximize and focus need the window on the current virtual desktop; nothing switches desktops. Focus does not restore a minimized window; `restore` does. The receipt reports the requested and measured bounds and the foreground separately from keyboard focus; Read again to see the new paint. These need the `windows-window-management` runtime (`windows-desktop` includes it); a runtime without it refuses, and keys or clicks are no substitute.
+`computer_window` samples the window's state and sends one command. Move and resize take integer Windows desktop pixels, not image, CSS or DIP coordinates, and need a normal window that is neither minimized nor maximized. Maximize and focus need the window on the current virtual desktop; nothing switches desktops. Focus does not restore a minimized window; `restore` does. The receipt reports the requested and measured bounds and the foreground separately from keyboard focus. Position and move must match exactly. A resize may land up to 2 px away in width or height and still ends `delivered`: Windows keeps a window that is not DPI aware in whole logical pixels on a scaled display (150%: some sizes are unreachable), so the measured size can differ from the request by that much, and the receipt shows both; Read again to see the new paint. These need the `windows-window-management` runtime (`windows-desktop` includes it); a runtime without it refuses, and keys or clicks are no substitute.
`computer_display` (YOLO) uses only modes the graphics driver lists; an unsupported size refuses and lists the supported ones. The change also affects what the human sees. Closing the computer session or the machine restores the replaced mode. Read displays and windows again afterwards: earlier display and window observations no longer work. A display of a Remote Desktop session has the one size its client sets: the displays listing and a refused change say so. The user changes it by resizing the client window, reconnecting with another size or the client's display settings; Windows scaling is the user's setting too. Computer use changes neither; to read small controls, Read a region in detail or make a viewport. Remote Desktop replaces the session's displays: while the user is connected, the only display is the client's; after they disconnect, the physical display with all its modes comes back under a new address. Read the displays again after the user connects or disconnects.
@@ -241,7 +241,7 @@ To set one up:
"lab": {
"ssh": "lab-wsl",
"runtime": "windows-desktop",
- "command": "/mnt/c/Users/user/AppData/Local/Programs/PiComputerUse/cua-driver-0.37.0-e2c256de/runtime/cua-driver.exe",
+ "command": "/mnt/c/Users/user/AppData/Local/Programs/PiComputerUse/cua-driver-0.37.0-33c4b82b/runtime/cua-driver.exe",
"node": "/mnt/c/Users/user/AppData/Local/Programs/PiComputerUse/node-v22.22.2-win-x64/node.exe",
"package": "/home/user/.local/share/pi-computer-use/package"
}