xiaoheizi1212/dsh-computer-use

Install

> You can also flip the whole capability on/off **live from the DeepSeek Harness GUI** — the plugin registers a `computer-use` settings section (Settings → `computer-use`), so `enabled`, `provider`, and the browser/import options above are editable without editing YAML.

### Core

| Option | Default | Meaning |
| --- | --- | --- |
| `enabled` | `true` | Master toggle — `false` turns the whole capability off |
| `provider` | `fake` | Backend: `fake` (tests) \| `playwright` (browser) \| `windows` (desktop) |
| `tools` | `true` | Register the model-facing tools |
| `confirmActions` | `true` | One-shot confirmation before risky `computer_act` calls |
| `visionProvider` / `visionModel` | — | llm-pi-ai route + model used by `computer_perceive analyze` |
| `visionMaxTokens` | `2000` | Vision output token cap |
| `allowedDomains` | `[]` | Hostnames the browser may act inside (empty = no restriction) |
| `windowsHelperCommand` | `''` | Native helper executable (defaults to the bundled `lib/native/win32-x64/dsh-computer-use-helper.exe`) |

### Browser (Playwright) session

| Option | Default | Meaning |
| --- | --- | --- |
| `browserHeadless` | `true` | Headless (default) or a visible window. `false` = 正常模式（弹窗） |
| `browserWindowState` | `normal` | Visible-window state: `normal` \| `maximized` \| `minimized`（先 launch、后应用状态） |
| `reuseBrowserProfile` | `false` | Use a persistent (dedicated) browser profile instead of an isolated context |
| `browserUserDataDir` | — | Persistent profile's "User Data" ROOT dir (non-default; e.g. `~/.dsh/browser-profiles/main`) |
| `browserProfileName` | `Default` | Profile directory name inside `browserUserDataDir` |
| `importCookies` | `false` | Import cookies so the isolated browser shares the user's logins |
| `importPasswords` | `false` | Import saved passwords for autofill |
| `importHistory` | `false` | Import browsing history as injected context |
| `cookiesFile` | — | Playwright storage-state JSON (`{ "cookies": [...] }`) loaded when `importCookies` |
| `passwordManagerCsv` | — | Password-manager CSV export (`name,url,username,password`) when `importPasswords` |

### Windows (desktop) provider

| Option | Default | Meaning |
| --- | --- | --- |
| `windowsWindowState` | `normal` | Target-window state: `normal` \| `maximized` \| `minimized`（minimized = 先激活后最小化） |

## Scripting: import cookies / passwords / history

The browser starts isolated (no cookies, no profile) by default. To give it your logged-in state:

**A. Cookie Bridge (recommended — works with Chrome 127+ App-Bound Encryption)**

Chrome 127+ encrypts cookies with App-Bound Encryption, so a separate process cannot read your existing profile's cookies. The Cookie Bridge sidesteps this by running **inside Chrome**: a small extension reads cookies via `chrome.cookies` (plaintext — Chrome decrypts them itself) and POSTs them to a local receiver.

Add xiaoheizi1212/dsh-computer-use to your DSH config (web profile) to enable.