@phnx-labs/computer-cli 0.1.8 → 0.1.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.10
4
+
5
+ - Over VNC, `click`, `right-click`, `type`, `type-text`, `key`, `scroll` and `drag` return once the screen has stopped changing (250 ms with no changed pixel, at most 1.5 s), instead of as soon as the events are written. Text typed right after a click no longer lands before the field has focus, and the next screenshot shows the result without a `sleep`.
6
+ - `drag --host vnc://…` works. It was refused with `vnc backend has no method 'drag'`; it now presses at `--from`, moves in 12 steps and releases at `--to`.
7
+ - `--char-delay` applies over VNC too; it was ignored there.
8
+ - `key --keys` takes several chords in order separated by commas (`--keys "Right,1,5,Tab"`), on every backend and from `computer run`; the screenshot is taken after the last one. A comma that is the key itself still works: `--keys ","`, `--keys "cmd+,"`. An empty `--keys` is an error. Before, only the VNC backend split on commas, so `cmd+,` was broken there.
9
+ - `scroll --dy/--dx` over VNC is a pixel delta, as on the other backends: about 50 px per wheel notch. It was one notch per unit, so `--dy -600` scrolled 600 notches and agents could not find a working value.
10
+ - The "coordinate mode moves your real cursor" note is no longer printed for a remote target (`--host`, `--device`), where it is not your cursor.
11
+
12
+ ## 0.1.9
13
+
14
+ - Removing a `Computer(<bundle-id>)` grant now applies to the next local `computer` invocation, as it already did under `agents computer`. Before, a direct call kept listing and driving the app until `computer reload`. Adding a grant still needs `computer reload`, a running `computer mcp` keeps the groups it read at startup, and remote TCP/VNC helpers keep their own policy. An inherited allowlist, including an empty one, still replaces the groups.
15
+
3
16
  ## 0.1.8
4
17
 
5
18
  - Add `scripts/generate-cli-docs.sh` with `--check` and `--out-dir`, downloadable command references in PR/release-branch CI, and a freshness check that also covers releases with tests/build skipped.
package/README.md CHANGED
@@ -61,7 +61,7 @@ computer key --host vnc://host:5900 --keys enter
61
61
  ```
62
62
 
63
63
  VNC provides screenshot and coordinate input (`click --x --y`, `type-text`,
64
- `key`). Accessibility verbs (`describe`, `get-text`, `click --id`, `type --id`)
64
+ `key`, `scroll`, `drag`); each input returns once the screen has settled. Accessibility verbs (`describe`, `get-text`, `click --id`, `type --id`)
65
65
  require a native driver and are not available over VNC.
66
66
 
67
67
  `computer run` drives an app from a natural-language task using an embedded model
@@ -268,13 +268,16 @@ Release with the repository's own script:
268
268
 
269
269
  ```sh
270
270
  bash scripts/release.sh # print the release plan (dry run)
271
- secrets exec npmjs.com -- bash scripts/release.sh --confirm
271
+ bash scripts/release.sh --confirm # push release/<version> and watch it publish
272
272
  ```
273
273
 
274
- Release requires a clean linked worktree at the reviewed `origin/main` commit. It
275
- builds every platform, verifies packed file lists and immutable package
276
- integrity, publishes the launcher and per-platform packages, and checks a
277
- registry install. Live desktop verification remains part of delivery.
274
+ `--confirm` runs from a clean linked worktree at the reviewed `origin/main` commit and
275
+ pushes `release/<version>`. The `release` workflow on that branch builds every platform,
276
+ runs the tests, verifies packed file lists and immutable package integrity, publishes the
277
+ per-platform packages and then the launcher, and tags `v<version>`. npm trusts that
278
+ workflow in the `npm-publish` environment through trusted publishing, so no npm token is
279
+ stored anywhere. The script then checks a registry install. Live desktop verification
280
+ remains part of delivery.
278
281
 
279
282
  Minification, obfuscation and bytecode compilation raise the bar for casual
280
283
  inspection; they are not a guarantee against reverse engineering. Keep
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@phnx-labs/computer-cli",
3
- "version": "0.1.8",
3
+ "version": "0.1.10",
4
4
  "description": "Native desktop automation over Accessibility, UI Automation and VNC",
5
5
  "type": "module",
6
6
  "bin": {
@@ -25,11 +25,11 @@
25
25
  "test": "bash scripts/test.sh"
26
26
  },
27
27
  "optionalDependencies": {
28
- "@phnx-labs/computer-cli-darwin-arm64": "0.1.8",
29
- "@phnx-labs/computer-cli-darwin-x64": "0.1.8",
30
- "@phnx-labs/computer-cli-linux-arm64": "0.1.8",
31
- "@phnx-labs/computer-cli-linux-x64": "0.1.8",
32
- "@phnx-labs/computer-cli-win32-x64": "0.1.8"
28
+ "@phnx-labs/computer-cli-darwin-arm64": "0.1.10",
29
+ "@phnx-labs/computer-cli-darwin-x64": "0.1.10",
30
+ "@phnx-labs/computer-cli-linux-arm64": "0.1.10",
31
+ "@phnx-labs/computer-cli-linux-x64": "0.1.10",
32
+ "@phnx-labs/computer-cli-win32-x64": "0.1.10"
33
33
  },
34
34
  "devDependencies": {
35
35
  "@modelcontextprotocol/sdk": "1.30.0",