dsh-tab-watchdog
Tab Watchdog for DeepSeek Harness Web：当工作区完成一轮工作（绿色）或需要关注（错误、问题、审批）时，标签页标题会带徽章闪烁。持久化的双部分插件（主机 + 浏览器）。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:andreagosto/dsh-tab-watchdog#38f0a085939e2db51e0066b342a84af738e0d15bTab Watchdog 以 dsh-tab-watchdog 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A persistent plugin for DeepSeek Harness Web: when one of your workspaces/sessions finishes a work round, errors out, or needs attention, the tab title blinks a 🟢/🟡 badge.
This is the "bundle" version (persistent, installable, shareable) of the Tab Watchdog dynamic plugin originally developed in Creator mode. Unlike a dynamic plugin it survives dsh restarts and browser reloads (F5).
Two halves in a single npm package, like the official plugins:
index.js) — profile composition row (cordis.patch.yml + dsh.bundle.patch). It makes the package a Loader entry: that row is what pulls the browser half into the boot manifest. No business logic here.lib/client.js, served via dsh.client + the ./client export) — a bundle in the window.__ModuleLoader__.load({ id, factory }) format. It subscribes to the Host events forwarded to the browser and handles everything (state, watermark, blink). No UI is added to the harness.The browser only receives the events on the dsh-api-remotes allowlist. The watchdog uses:
| Event | Level | Label |
|---|---|---|
api-session/status(sessionId, running=false) | 🟢 green | "Finished a work round" |
api-session/error(sessionId, message) | 🟡 yellow | "Error…" |
user-questions/request(...) (passive) | 🟡 yellow | "Asking for a response" |
approval/request(...) (passive) | 🟡 yellow | "Requires approval" |
The user-questions/request and approval/request observers are passive: they always call next() so they never interfere with the official question/approval UI. If another handler consumes a request before the watchdog sees it, the yellow may not show; the green/error emit events are always delivered to every listener in parallel, so they are guaranteed.
Note: workflow/end, agent/status, and goal/changed are not forwarded to the browser in this version's allowlist; observing them would require host-side aggregation over a custom channel (out of scope by design).
🟢n 🟡m · <title> and <title>.running=true), its pending entries are removed.running=false does not downgrade it to green.web profile)From the plugin checkout:
# from the directory that contains dsh-tab-watchdog/
npx @deepseek-ai/dsh@latest plugin --profile web add ./dsh-tab-watchdog
Then restart dsh web. The browser half activates on the next reload/startup. The added row is the tab-watchdog entry in the profile's cordis.yml.
Removal:
npx @deepseek-ai/dsh@latest plugin --profile web remove dsh-tab-watchdog
dsh pluginforwards to pnpm inside the profile. If pnpm is not installed:corepack enableornpm i -g pnpm.
The browser half source is src/client.js (a CJS fragment living inside the loader factory). The lib/client.js artifact is committed (no build step at git-install time).
npm run build # regenerates lib/client.js from src/client.js
npm test # verify (bundle structure) + smoke (blink/watermark logic)
No prepare/monorepo toolchain needed: out-of-tree plugins cannot use the internal clientBundle preset, so the loader format is reproduced by hand (scripts/build.mjs).
The package declares dsh.bundle.patch, so it installs as a profile bundle. Because lib/client.js and index.js are committed artifacts, a git install works without prepare:
npx @deepseek-ai/dsh@latest plugin --profile web add github:andreagosto/dsh-tab-watchdog
For discoverability, the GitHub repository carries the dsh-plugin topic (see the official deepseek-harness README, "Community and support"). Alternatively: npm publish, then dsh plugin --profile web add dsh-tab-watchdog.
@deepseek-ai/dsh 0.1.2-rc.1 (mind the "breaking changes" notice on rc prereleases).npm test, but verify it live in your own profile.dsh plugin remove (or set disabled: true on the row in the profile patch).MIT