dsh-web-ui-notify
为 DeepSeek Harness 的审批、问题和回合完成提供桌面通知——这样无论是 DSH 还是你，都不会在浏览其他标签页时一直等待。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:bill9109/dsh-web-ui-notify#83737f2046e01363d610d74f451c8c0fb8b8d57bWeb Ui Notify 以 dsh-web-ui-notify 发布，当前版本为 0.1.4。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Install: dsh plugin --profile web add github:omdsh-dev/dsh-web-ui-notify
A DeepSeek Harness Web UI client plugin: when a tool needs approval, DSH asks you a question, or a turn finishes while you are looking at another tab, it pops a system desktop notification — so neither DSH nor you end up waiting.
While you browse other pages, DSH needs human confirmation (tool approvals, questions) or finishes a round of work, and the Web UI in the foreground tab is the only place it asks. If you are looking anywhere else, the request waits silently. This plugin moves those moments onto your desktop: a native system notification appears, names the session, and clicks back into the conversation.
The plugin is a DSH bundle (package.json declares dsh.bundle + dsh.client). Install it into the web profile with the standard dsh plugin mechanism — no DSH source changes and no hand-written patch:
dsh plugin --profile web add github:omdsh-dev/dsh-web-ui-notify
Internally the command runs pnpm add <spec> in the profile directory and automatically appends packages that declare dsh.bundle to dsh.profile.bundles. You can also clone it and install from a local path (for development — rebuild and it takes effect):
dsh plugin --profile web add /path/to/dsh-web-ui-notify
The repository ships its build output (lib/), so the plugin works right after installing — no build step needed. It has zero runtime dependencies: the browser-side requires (react, react/jsx-runtime, ui-slots) resolve through DSH's own frontend module table, not npm.
Older DSH (before the profile system) installed via
pnpm --filter @deepseek-ai/dsh add+config.yaml; since the 20260806 snapshot the profile flow above is the way. If your DSH is still old, use the historical README (visible in git history).
After installing, restart the Web UI (the way you normally start DSH) and refresh the browser page — the plugin takes effect.
dsh plugin --profile web update github:omdsh-dev/dsh-web-ui-notify
For a local-path installation, run add again against the replacement checkout. User settings (the Settings → General toggle) live in the profile's Settings provider and survive upgrades.
dsh plugin --profile web remove dsh-web-ui-notify
The command runs pnpm remove <pkg> in the profile directory and removes it from dsh.profile.bundles. After uninstalling, restart web and hard-refresh the browser.
After installation you must also grant browser notification permission, otherwise the plugin stays silent — without permission the browser simply blocks notifications.
Then switch to another tab — approvals, questions, or finished turns produce system notifications, and clicking one brings you back to handle it.
The settings row has four states:
| Status | Meaning |
|---|---|
| Enabled | Working normally |
| Not granted | Click the button to grant |
| Blocked by browser | Previously denied — change the site setting back to Allow; the button alone will not help |
| Unsupported | The environment has no Notification API |
| Symptom | Resolution |
|---|---|
| No notifications appear | Confirm the toggle in Settings → General is Enabled, the browser permission for the DSH site is Allow, and on macOS the browser is allowed under System Settings → Notifications; then switch to another tab — the plugin only notifies while you are away |
| Notifications worked, then stopped after a restart | The browser may have reset site permissions; re-grant, or re-enable the toggle if the settings row shows a different state |
| "Blocked by browser" | The site permission was previously denied — change it back to Allow in the browser's site settings; clicking Enable alone will not help |
| "Unsupported" | The environment has no Notification API (e.g. an old or unusual browser); desktop notifications cannot work there |
| Plugin not in Settings → General after install | The plugin only appears after the Web UI is restarted and the page hard-refreshed; verify the bundle row is in the profile (`dsh --profile web --dump-config |
pnpm install
pnpm run build # tsc + tsdown -> lib/ (committed)
pnpm test # vitest: browser-plugin + settings-row suites
pnpm run build emits the host + client bundles into lib/, which is committed so consumers install without building. The test suite covers plugin wiring on a real cordis context and the settings row in jsdom. Changes that alter the plugin's visible surface (which events notify, the settings row, locales) should add or update coverage in tests/.
BSD-3-Clause