@agent-sh/computer-use-linux 0.7.10 → 0.7.12
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/README.md +31 -11
- package/npm/README.md +3 -1
- package/npm/bin/computer-use-linux.js +4 -0
- package/npm/install.js +45 -4
- package/package.json +1 -1
- package/pi/extension/THIRD_PARTY_NOTICES.txt +2 -2
- package/pi/extension/generated-tools.ts +3 -3
- package/pi/extension/index.ts +15 -0
- package/pi/extension/mcp-client.bundle.cjs +29 -29
- package/skills/computer-use-linux/SKILL.md +6 -2
- package/skills/computer-use-linux/references/pi-setup.md +4 -1
|
@@ -174,7 +174,8 @@ directly to a window-relative click.
|
|
|
174
174
|
- `click`, `drag`, `press_key`, `type_text`, `perform_action`, and `set_value` can change real application state.
|
|
175
175
|
- When ydotool is selected, `ydotoold` should run as a per-user service with its socket under `/run/user/$UID`, not as a system-wide service.
|
|
176
176
|
- The optional ydotool backend requires version 1.0.3 or newer; `doctor` rejects older or semantically incompatible CLIs even when `ydotoold` is running.
|
|
177
|
-
- On COSMIC, the standard npm, Cargo, and install-script paths install the `computer-use-linux-cosmic` helper automatically. Manual binary installs must copy
|
|
177
|
+
- On COSMIC, the standard npm, Cargo, and install-script paths install the `computer-use-linux-cosmic` helper automatically. Manual binary installs must copy it too.
|
|
178
|
+
- An on-screen indicator shows the user each action: a cursor glides to pointer targets and keycaps or typed text appear for keyboard input. Pointer actions wait about 350 ms so the cursor lands first. The indicator is hidden before screenshots and is never part of captured images.
|
|
178
179
|
|
|
179
180
|
## Verification
|
|
180
181
|
|
|
@@ -194,7 +195,10 @@ Ready output should have:
|
|
|
194
195
|
- `can_build_accessibility_tree: true`
|
|
195
196
|
- `can_query_windows: true`
|
|
196
197
|
- `can_send_development_input: true`
|
|
197
|
-
- `
|
|
198
|
+
- `screenshot_capture_status: "unverified"`
|
|
199
|
+
- `can_capture_screenshots: false`
|
|
198
200
|
- `blockers: []`
|
|
199
201
|
|
|
202
|
+
Doctor detects screenshot routes without capturing or requesting consent. Treat unverified capture as a warning. Call `get_app_state` with `include_screenshot: true` to verify it: a successful raw capture reports `screenshot_capture_status: "verified"` and `can_capture_screenshots: true`; a failure reports `failed` and keeps the boolean false. Inspect `screenshot_error` for the full backend cause.
|
|
203
|
+
|
|
200
204
|
Then test with your agent by calling the `doctor` tool or asking the agent to list desktop windows.
|
|
@@ -137,5 +137,8 @@ Ready output has:
|
|
|
137
137
|
- `can_build_accessibility_tree: true`
|
|
138
138
|
- `can_query_windows: true`
|
|
139
139
|
- `can_send_development_input: true`
|
|
140
|
-
- `
|
|
140
|
+
- `screenshot_capture_status: "unverified"`
|
|
141
|
+
- `can_capture_screenshots: false`
|
|
141
142
|
- `blockers: []`
|
|
143
|
+
|
|
144
|
+
Doctor detects screenshot routes without capturing or requesting consent. Treat unverified capture as a warning. Call `get_app_state` with `include_screenshot: true` to verify it: a successful raw capture reports `screenshot_capture_status: "verified"` and `can_capture_screenshots: true`; a failure reports `failed` and keeps the boolean false. Inspect `screenshot_error` for the full backend cause.
|