Skip to content
Back to search

dsh-computer-use

为 DeepSeek Harness 提供电脑控制插件:新鲜 Accessibility 观测、过期状态拒绝、作用域权限与安全输入(目前支持macos)|Accessibility-first macOS Computer Use bundle for DSH with fresh observations, stale-state rejection, scoped permissions, and safe input.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Anionex/dsh-computer-use with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Anionex/dsh-computer-use'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/anionex--dsh-computer-use/badge.svg)](/listings/anionex--dsh-computer-use)

HTML

<a href="/listings/anionex--dsh-computer-use"><img src="/api/listings/anionex--dsh-computer-use/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

- macOS 14 or newer. - DeepSeek Harness with a Web or Headless Profile and the Skill Tool mounted. - macOS Accessibility permission for observation and native actions. - macOS Screen Recording permission only when a screenshot is requested. - Node.js `^22.19.0` or `>=24.0.0` when building this repository.

Install the Web and Headless bundles directly from npm:

> [!IMPORTANT] > The published package name is `@anionex/dsh-computer-use`. The former > `@dsh-external/dsh-computer-use` name was never published to npm and is not > installable; update any old profile or manifest references before installing.

dsh plugin --profile web add @anionex/dsh-computer-use
dsh plugin --profile headless add @anionex/dsh-computer-use

dsh --profile web --dump-config | grep computer-use
dsh --profile headless --dump-config | grep computer-use

For local development, replace the package name with an absolute checkout path.

Restart a running `dsh web` host after changing the installed plugin, then start a new Session so the host reloads the Bundle and Skill catalog.

Load the Skill in that Session:

/dsh-computer-use

The existing `/computer-use` Skill remains available for older sessions. If another installed Skill uses that name, load `/dsh-computer-use` to activate this plugin.

Then try:

> Use Computer Use to inspect the running DSH Computer Use Fixture, enable its deterministic option, and report the fresh status. Prefer Accessibility elements and do not reuse an old observation.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 336 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # DSH Computer Use
  2. [![X (Twitter)](https://img.shields.io/badge/-@anion__ex-000000?style=flat-square&logo=x&logoColor=white)](https://x.com/anion_ex)
  3. [![License: MIT](https://img.shields.io/badge/license-MIT-2f855a.svg)](LICENSE)
  4. ![macOS](https://img.shields.io/badge/macOS-14%2B-111827.svg)
  5. ![Universal binary](https://img.shields.io/badge/native-arm64%20%2B%20x86__64-2563eb.svg)
  6. ![DeepSeek Harness](https://img.shields.io/badge/DeepSeek%20Harness-Bundle-5b50ed.svg)
  7. **Native macOS control for DeepSeek Harness that keeps your real cursor and foreground application alone by default; the Bundle may bring the target app forward before keyboard input for reliable typing.**
  8. DSH Computer Use gives an Agent fresh Accessibility observations, exact process/window targeting, stale-state rejection, scoped application access, and verified post-action state. Semantic Accessibility comes first; mouse, drag, wheel, and keyboard fallback are routed to the selected process instead of the global desktop.
  9. English | [中文](README.zh.md)
  10. <p align="center">
  11. <img src="assets/computer-use-demo.gif" width="960" alt="DSH Computer Use demonstrates clicking, typing, dragging to select text, and bold formatting with its virtual cursor." />
  12. </p>
  13. Quick demo (2×): clicks, text entry, drag selection, and formatting with the visible Agent cursor.
  14. ## Why it is different
  15. Accessibility permission lets a process inspect and operate macOS UI elements, but the permission itself does not prevent focus stealing or cursor movement. Those behaviors depend on the input route.
  16. The default DSH Computer Use route is deliberately non-interfering:
  17. - **No system-cursor movement:** the helper contains no cursor-warp path.
  18. - **No global pointer injection:** click, scroll, and drag fallback use a pid/window-targeted SkyLight route, not the global HID event stream.
  19. - **No pointer-triggered activation:** semantic Accessibility, process-targeted pointer input, and `keyboardPolicy: preserve` run without activation; `keyboardPolicy: activate` (Bundle default) brings the target app forward before keyboard fallback, matching Codex Computer Use.
  20. - **A separate Agent cursor:** click, scroll, and drag actions animate a click-through, nonactivating software cursor while the macOS system cursor remains untouched. It appears only while the exact target application is frontmost and follows a speed/acceleration-shaped curved path. Click and scroll wait for arrival before input; drag reaches and presses at the start point, then tracks the destination while the native drag runs.
  21. - **No blind replay:** every action is tied to an exact, unexpired observation and returns fresh state.
  22. The result is a native action layer that can operate many background applications while the user continues working in the current foreground application.
  23. ## What it adds
  24. - **Observe before acting.** Return a bounded Accessibility tree, indexed elements, exact app/process/window metadata, permission state, and an optional screenshot Artifact.
  25. - **Bind actions to state.** Every element exposes an observation-local index and opaque `targetHandle`; exact lookup remains compatible, while explicitly allowed rebinding accepts only a unique native or semantic identity inside the same process and window.
  26. - **Prefer semantic input.** Use `AXPress`, editable values, selected-text assignment, and advertised Accessibility actions before pointer fallback.
  27. - **Route fallback to the target.** Keyboard input goes to the selected pid; pointer input goes to the selected pid and `CGWindowID` with window-local coordinates, resolving the app window under the point so arbitrary screen coordinates work.
  28. - **Return fresh evidence.** Every successful action settles for a bounded interval and returns a new full or diff observation.
  29. - **Scope application access.** Read and control leases are separated by Agent, Session, turn, and exact bundle id; high-impact actions require one-use confirmation.
  30. - **Keep the model surface focused.** Execution Tools appear only after the current Agent loads the Computer Use Skill.
  31. ## Proof: a never-active background fixture
  32. The repository includes a deterministic AppKit fixture and a universal native helper. Release tests start the fixture with `open -g` in background mode, then use the same protocol exposed to the Agent.
  33. ```text
  34. observe exact bundle id + pid
  35. -> element: "Targeted pointer probe", no AXPress action
  36. -> computer_click with observationId + element index + allowCoordinateFallback
  37. -> fresh observation
  38. -> activation "not-requested"; pointerRouting "target-process"
  39. -> status "Status: pointer click"
  40. ```
  41. The fixture records every `applicationDidBecomeActive` callback. An independent native monitor also samples the system cursor and frontmost pid every millisecond throughout click, scroll, and drag. The default release path must not increase `activationCount`; it also requires unchanged cursor coordinates, an unchanged frontmost pid, exact click/scroll counts, and one complete down/up drag gesture.
  42. See [Foreground-safe input policy](docs/interaction-policy.md) for the requirements, architecture, decisions, evidence, and compatibility limits.
  43. ## Scope
  44. `dsh-computer-use` is the native **action layer**. It does not replace narrower interfaces:
  45. - browser tasks should use browser automation and DOM/CDP state;
  46. - APIs, CLIs, and purpose-built application plugins remain preferable when available;
  47. - OCR, visual grounding, and pixel interpretation should use the separately installed `dsh-vision-toolkit`: load the `vision-tools` Skill and pass the exact screenshot Artifact path to `vision_glance`, `vision_ground`, `vision_detect`, `vision_crop`, or `vision_long_screenshot_ocr`; do not replace those tools with shell-driven `tesseract`, `screencapture`, or ad hoc Swift/Python OCR;
  48. - domain bundles such as `dsh-design` can compose Computer Use when a workflow crosses into a native application.
  49. ## Quick start
  50. ### Prerequisites
  51. - macOS 14 or newer.
  52. - DeepSeek Harness with a Web or Headless Profile and the Skill Tool mounted.
  53. - macOS Accessibility permission for observation and native actions.
  54. - macOS Screen Recording permission only when a screenshot is requested.
  55. - Node.js `^22.19.0` or `>=24.0.0` when building this repository.
  56. Install the Web and Headless bundles directly from npm:
  57. > [!IMPORTANT]
  58. > The published package name is `@anionex/dsh-computer-use`. The former
  59. > `@dsh-external/dsh-computer-use` name was never published to npm and is not
  60. > installable; update any old profile or manifest references before installing.
  61. ```sh
  62. dsh plugin --profile web add @anionex/dsh-computer-use
  63. dsh plugin --profile headless add @anionex/dsh-computer-use
  64. dsh --profile web --dump-config | grep computer-use
  65. dsh --profile headless --dump-config | grep computer-use
  66. ```
  67. For local development, replace the package name with an absolute checkout path.
  68. Restart a running `dsh web` host after changing the installed plugin, then start a new Session so the host reloads the Bundle and Skill catalog.
  69. Load the Skill in that Session:
  70. ```text
  71. /dsh-computer-use
  72. ```
  73. The existing `/computer-use` Skill remains available for older sessions. If another
  74. installed Skill uses that name, load `/dsh-computer-use` to activate this plugin.
  75. Then try:
  76. > Use Computer Use to inspect the running DSH Computer Use Fixture, enable its deterministic option, and report the fresh status. Prefer Accessibility elements and do not reuse an old observation.
  77. ## How it works
  78. ```mermaid
  79. flowchart LR
  80. A["Select exact bundle id and pid"] --> B["Acquire scoped read access"]
  81. B --> C["Observe AX tree and optional screenshot"]
  82. C --> D["Choose target handle, index, or window-relative point"]
  83. D --> E["Acquire control and optional one-use confirmation"]
  84. E --> F["Re-observe and validate exact target"]
  85. F --> G{"Input route"}
  86. G -->|"Semantic"| H["Accessibility action or value"]
  87. G -->|"Keyboard"| I["Post to target pid"]
  88. G -->|"Pointer"| J["Post to target pid + window"]
  89. H --> K["Wait for settlement"]
  90. I --> K
  91. J --> K
  92. K --> L["Return fresh full or diff observation"]
  93. ```
  94. Every observed element has an observation-local compatibility index and an opaque `targetHandle`. Index-only actions retain exact locator behavior. A low-risk element action may pass `targetHandle` with `allowRebind: true`; immediately before input, the provider-independent resolver obtains fresh Accessibility state and checks, in order, the original locator, a unique provider-native identifier such as macOS `AXIdentifier`, then one unique semantic match over role, accessible name, advertised actions, and stable ancestor fingerprint. The resolver keeps the exact bundle id, pid, and selected-window identity, and fails closed with `COMPUTER_TARGET_AMBIGUOUS` or `COMPUTER_TARGET_LOW_CONFIDENCE` instead of guessing. Coordinate actions still require the complete referenced window state to remain current.
  95. Successful element actions report `resolution.mode`, `confidence`, `candidateCount`, and `targetChanged`. A sensitive target that needs rebinding invalidates the prior one-use confirmation and returns `COMPUTER_TARGET_REBIND_REQUIRES_CONFIRMATION`; the caller must observe the current UI and confirm the newly selected handle. Visual coordinates are not target handles and never authorize sensitive rebinding. Provider-native visual hit-testing is not part of this foundation release and remains follow-up work.
  96. The default interaction policy is:
  97. ```yaml
  98. interaction:
  99. focusPolicy: preserve
  100. keyboardPolicy: activate
  101. pointerInputPolicy: targeted
  102. cursorVisualization: visible
  103. cursorSpeedPxPerSecond: 1600
  104. cursorAccelerationPxPerSecondSquared: 6000
  105. cursorClickDelayMs: 90
  106. cursorAutoHideMs: 0
  107. ```
  108. `cursorVisualization: visible` displays the Agent's own non-interactive cursor for click, scroll, and drag only while the selected application is frontmost. It never replaces or moves the macOS system cursor. Set it to `hidden` when visual feedback is unwanted. `pointerInputPolicy: deny` disables coordinate click/fallback, scroll, and drag. `keyboardPolicy: activate` (Bundle default) makes `type-text` keyboard fallback and `press-key` reliable by activating the target app first; `focusPolicy: activate` is the broader compatibility mode that also activates and freshly revalidates before pointer cursor movement and input.
  109. The cursor is a 28x28 transparent whole-image cursor (Cursor arrow plus DeepSeek whale, `assets/cursor.png`) with the hotspot at the image's top-left corner. It is a separate process, click-through, nonactivating, and bound to the exact observed pid, window, frame, and current frontmost application. It disappears when that binding stops matching. Travel time is derived from distance, maximum speed, and acceleration; a short curved path plus symmetric acceleration/deceleration keeps the default motion legible, while high values reduce it to a few visible frames. Click input is sent only after native arrival and the configured dwell. For drag, that same sequence reaches the start point before the targeted native drag and endpoint cursor travel begin together.
  110. The helper executable is an internal DSH transport rather than a public authorization API. It requires an isolated process group plus parent-owned standard transports, so ordinary shell redirection fails closed before command parsing. This is defense in depth, not authentication against arbitrary code running as the same macOS user: a deliberately constructed detached parent can reproduce that transport topology. Use the registered Tools so application leases, sensitive-action confirmation, and host policy checks remain in force; `danger-full-access` must not be treated as protection against direct native invocation.
  111. Successful action results include:
  112. ```ts
  113. activation: 'not-requested' | 'already-frontmost' | 'activated'
  114. pointerInput: boolean
  115. pointerRouting: 'none' | 'target-process'
  116. resolution?: {
  117. mode: 'exact-locator' | 'native-identifier' | 'semantic-rebind'
  118. confidence: number
  119. candidateCount: number
  120. targetChanged: boolean
  121. }
  122. agentCursor?: { visible: false; reason?: string }
  123. effect: {
  124. observedStateChanged: boolean
  125. observedForMs: number
  126. note?: string
  127. }
  128. ```
  129. `effect.observedStateChanged` compares the window title, id and frame plus the Accessibility element tree. It does not prove causation and cannot see pixel-only, transient, remote, or otherwise external effects. `agentCursor` appears only when the separate Agent cursor was expected but could not be shown or validated.
  130. The model cannot override these host policies through Tool arguments.
  131. ## Model Tools
  132. The Bundle initially contributes only `computer_use_activate`. Loading the Skill exposes the focused execution vocabulary for that Agent.
  133. <details>
  134. <summary>Show the complete Tool vocabulary</summary>
  135. | Tool | Purpose |
  136. |---|---|
  137. | `computer_list_apps` | List bounded user-facing applications with bundle id, pid, frontmost state, and permission diagnostics |
  138. | `computer_observe` | Return a fresh full/diff Accessibility observation and optional screenshot Artifact |
  139. | `computer_click` | Prefer `AXPress`; accept an exact index or opaque target handle, with optional safe rebinding, before target-process coordinate fallback |
  140. | `computer_set_value` | Set or clear an editable Accessibility value through an exact index or opaque target handle without using the clipboard |
  141. | `computer_type_text` | Insert Unicode through Accessibility or process-targeted keyboard input; `method: keyboard` skips unreliable AX insertion without changing the host focus policy |
  142. | `computer_press_key` | Send one key from a finite vocabulary to the selected process, with optional modifiers |
  143. | `computer_scroll` | Send bounded directional scrolling to the selected process and window at a resolved element or window/screen coordinate |
  144. | `computer_drag` | Drag between two window/screen points in the referenced observation |
  145. | `computer_perform_action` | Execute one Accessibility action advertised by an exact or safely rebound selected element |
  146. | `computer_wait` | Poll one bounded text/role/title condition and return fresh state without modifying the app |
  147. | `computer_confirm` | Obtain a one-use token bound to one exact sensitive action |
  148. No Tool accepts AppleScript, JXA, shell, Swift, Objective-C, native selectors, arbitrary Accessibility constants, or source code.
  149. </details>
  150. ## Observation, permissions, and sensitive actions
  151. An observation contains an opaque id and expiry, exact app identity, frontmost/window metadata, bounded tree text, current elements with opaque target handles, optional screenshot metadata, and permission state. Target handles expose no provider object reference or native identifier. Secure text values are emitted as `[secure]`; they do not enter target descriptors, tree text, Tool results, screenshot metadata, or native errors. A screenshot can still contain other visible application data and should be treated as sensitive.
  152. For Electron applications, the helper requests document accessibility through AXManualAccessibility and waits a bounded time for web controls to appear. For a web element in an app that supports this writable attribute, allowCoordinateFallback=true opts into one target-process pointer click at the element center before any AX press. Other apps (including WebKit web areas), native controls, and calls without this opt-in keep the semantic AX path. A successful AX press is never retried based on an unchanged tree: its effect may be delayed or external. Host pointer and activation policies still apply.
  153. Coordinate actions accept three spaces: `window` and `screen` are measured in points, the unit of Accessibility frames, while `screenshot` is measured in the observation screenshot's pixels. A screenshot is captured at the window's backing scale without the drop shadow, so the image is a direct rendering of the window frame and `screenshot.pixelScale` reports pixels per point (normally `2` on Retina). Coordinates read off the screenshot image must therefore be passed as `coordinateSpace: 'screenshot'`; passing them as `window` points offsets the click by the pixel scale — on a 2x display a click intended for the middle of a window lands at twice its offset and can miss the control entirely. The service converts screenshot pixels to window points before any input is sent, and rejects window coordinates that exceed the frame but fit the screenshot with an error naming the scale.
  154. The technical access model has two exact-bundle-id leases:
  155. - `read`: inspect Accessibility state and a requested screenshot;
  156. - `control`: send UI input to the selected application.
  157. Without a configured grant, DSH asks for approval. Read approval lasts for the Session; control approval lasts for the current turn. A user rejection is final for that app and scope for the rest of the Session.
  158. The Bundle keeps Session-wide read grants and rejected app/scope decisions in its own `computer_use_state` storage-domain sidecar, fenced by the Session header's `createdAt` and `cwd`. It does not add Computer Use events to the official Session log or modify DSH Core. The Web Profile already composes `@deepseek-ai/dsh-storage-domain`; a custom Profile must compose it before this Bundle if interactive read grants or durable rejections are needed. Exact grants configured in Settings remain available without storage-domain, and an allowed control decision remains process-local for the current turn. When a durable interactive decision cannot be stored, the operation fails clearly instead of silently weakening its lifetime.
  159. The DSH `danger-full-access` preset uses `approval/policy: never`, so an ungranted app is policy-blocked before any prompt. The plugin reports an actionable `COMPUTER_PERMISSION_REQUIRED` error and does not record that outcome as a user rejection. Add the exact bundle id in Computer Use Settings or use a preset whose approval policy is `ask`.
  160. High-impact communication, sensitive-data transmission, irreversible deletion, account/security/privacy changes, unrequested installation, legal acceptance, and financial completion beyond explicit authorization require `computer_confirm` immediately before execution. The token is short-lived, one-use, and bound to the exact app, process, observation, target handle, and action. Grants do not bypass it. If resolution moves beyond the exact locator, the token is invalidated and a fresh observation plus confirmation is required.
  161. ## macOS permissions and native integrity
  162. The Web Settings section reports helper integrity, Accessibility and Screen Recording status, active generation, interaction policy, limits, and exact application grants. Its buttons can open the relevant macOS privacy pane after a user click; the plugin cannot grant TCC permission itself.
  163. Accessibility and Screen Recording are UI permissions, not filesystem permissions. Normal use stays under DSH `workspace-write`: screenshots remain in the Session workspace, transient files use Session-private temporary storage, and the Bundle does not require `danger-full-access`.
  164. The committed helper is an ad-hoc-signed universal `arm64` + `x86_64` binary targeting macOS 14 or newer. [`native/macos/manifest.json`](native/macos/manifest.json) pins its SHA-256, source digest, architectures, and deployment target. `pnpm run check:native` also checks the target-process-only pointer route and rejects system-cursor warp or global pointer-post symbols.
  165. ## Configuration
  166. <details>
  167. <summary>Show Bundle configuration fields</summary>
  168. | Field | Purpose |
  169. |---|---|
  170. | `observationTtlMs` | Lifetime of an observation before reuse is rejected; default `0` disables expiry, or set any value up to `86400000` ms (24 hours) |
  171. | `confirmationTtlMs` | Lifetime of a one-use sensitive-action confirmation |
  172. | `actionTimeoutMs` | Hard native action timeout from `1000` to `120000` ms |
  173. | `settleMs` | Interval between post-action state checks from `0` to `10000` ms |
  174. | `maxSettleMs` | Maximum post-action settlement budget from `100` to `60000` ms |
  175. | `maxNodes` / `maxDepth` / `maxTextBytes` | Accessibility traversal and model-visible text bounds |
  176. | `maxScreenshotBytes` | Maximum PNG Artifact size |
  177. | `artifactRoot` | Workspace-relative screenshot directory |
  178. | `helper.path` | Optional explicit external helper executable; omitted, empty, or whitespace-only values use the packaged managed helper |
  179. | `helper.allowSourceBuild` | Permit an explicit managed-source rebuild when the committed helper is absent; default `false` |
  180. | `interaction.focusPolicy` | `preserve` (default) avoids target-app activation; `activate` explicitly permits it and requires re-observation/revalidation |
  181. | `interaction.keyboardPolicy` | `preserve` keeps keyboard events routed without activation; `activate` (Bundle default) activates the target app before keyboard fallback |
  182. | `interaction.pointerInputPolicy` | `targeted` (default) permits pid/window-targeted pointer input; `deny` disables click fallback, scroll, and drag |
  183. | `interaction.cursorVisualization` | `visible` (default) shows the separate Agent cursor; `hidden` disables only the overlay |
  184. | `interaction.cursorSpeedPxPerSecond` | Requested maximum Agent-cursor speed; default `1600`, range `100` to `50000` pixels per second; the 48 to 2000 ms motion safety bound takes priority at extreme distance/value combinations |
  185. | `interaction.cursorAccelerationPxPerSecondSquared` | Agent-cursor acceleration and deceleration; default `6000`, range `100` to `500000` pixels per second squared |
  186. | `interaction.cursorClickDelayMs` | Dwell after arrival and before click/drag press feedback and native input; default `90`, range `0` to `1000` ms |
  187. | `interaction.cursorAutoHideMs` | Idle time before the Agent cursor hides; default `0` keeps it visible while the target remains frontmost and bound, or set a finite value up to `30000` ms |
  188. | `allowAllApps` | Grant `read` and `control` to every running app; default `false`. When enabled, exact `grants` are ignored |
  189. | `grants` | Exact non-wildcard bundle-id read/control policy; `control: true` implies read |
  190. </details>
  191. The deprecated 0.2.x `interaction.cursorMotionMs` field remains accepted so existing Settings documents load, but it is ignored at runtime and removed the next time Web Settings saves the configuration.
  192. Settings updates replace the active provider generation only after validation and health checks pass. Replacement invalidates existing observations and pending confirmations.
  193. ## Status and limitations
  194. - Status: early `0.3.0`; model-facing and provider behavior may change before a stable release.
  195. - The current provider is macOS-only. Windows UI Automation and Linux providers are not implemented.
  196. - On non-macOS hosts the plugin degrades gracefully: the DSH profile starts normally, Computer Use Tools and the Skill are not registered, and Web Settings reports `COMPUTER_UNSUPPORTED_PLATFORM` instead of failing startup.
  197. - Target-process pointer delivery uses dynamically resolved SkyLight SPI. If it is unavailable, pointer fallback fails closed rather than switching to global input.
  198. - The clicked point must fall inside an on-screen window of the selected app; the helper resolves the topmost matching window so ambiguous frame/title matches no longer block coordinate actions. Minimized, hidden, or windowless targets fail closed.
  199. - Custom canvases, games, hardened input surfaces, and future macOS releases may reject target-process pointer or keyboard events. Prefer semantic Accessibility whenever possible.
  200. - `focusPolicy: activate` and `keyboardPolicy: activate` are intentionally disruptive and exist as operator-selected compatibility modes.
  201. - A target application may change its own activation or focus as a side effect of an accepted action.
  202. - The package captures requested discrete observations, not a live desktop feed.
  203. - Browser work should continue to use browser automation because DOM/CDP state is narrower and more precise.
  204. - The public npm package installs into both Web and Headless profiles as `@anionex/dsh-computer-use`.
  205. ## Development and release verification
  206. Place this repository beside a DeepSeek Harness checkout so TypeScript and Vitest resolve the exact DSH peer declarations and runtime modules:
  207. ```text
  208. workspace/
  209. ├── packages/
  210. ├── vendor/
  211. └── dsh-computer-use/
  212. ```
  213. Then run:
  214. ```sh
  215. pnpm install --frozen-lockfile
  216. pnpm run build
  217. DSH_COMPUTER_USE_REQUIRE_TCC=1 pnpm test
  218. pnpm run check:native
  219. pnpm pack --dry-run
  220. pnpm run validate
  221. ```
  222. `pnpm run validate` runs the keyless local and clean Web/Headless Profile lanes. The real-model release lane needs `DEEPSEEK_API_KEY` and accepts an optional `DEEPSEEK_BASE_URL`:
  223. ```sh
  224. pnpm run validate:model
  225. # or keyless validation followed by the real-model lane
  226. pnpm run validate:release
  227. ```
  228. ## Removal
  229. ```sh
  230. dsh plugin --profile web remove @anionex/dsh-computer-use
  231. dsh plugin --profile headless remove @anionex/dsh-computer-use
  232. ```
  233. Removing or disabling the Bundle unregisters the Skill and Tools, cancels helper work, releases process-local Agent observations, turn control grants, and confirmations, closes its storage-domain handle, and removes Web contributions. Existing screenshot files and the plugin-owned `computer_use_state` sidecar remain for explicit user cleanup.
  234. ## Security, community, and support
  235. - Report suspected vulnerabilities privately through [SECURITY.md](SECURITY.md).
  236. - Read [CONTRIBUTING.md](CONTRIBUTING.md) before changing code or documentation.
  237. - Use [SUPPORT.md](SUPPORT.md) for installation, permission, configuration, and workflow questions.
  238. - Follow the [Code of Conduct](CODE_OF_CONDUCT.md) in project spaces.
  239. - See [CHANGELOG.md](CHANGELOG.md) for release history.
  240. - See [FUNDING.md](FUNDING.md) to support maintenance without purchasing roadmap control or private support.
  241. ## About
  242. DSH Computer Use is maintained by [anionex](https://anionex.me/). If you would like to follow my future work, [follow me on X](https://x.com/anion_ex) or [GitHub](https://github.com/Anionex).
  243. ## License
  244. [MIT](LICENSE) © 2026 anionex.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.