dsh-task-board
DSH 任务看板插件：为 DSH Web GUI 添加看板标签页（Chat/Trajectory/Tasks），支持拖动以执行真实 agent 运行。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:linsibin/dsh-task-board#404171509f93046e060e0265898483dc0fa76e1d
Task Board 以 dsh-task-board 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A task-board client plugin for DeepSeek Harness Desktop. Adds a 「Tasks」 tab next to Chat / Trajectory in the conversation header, with a three-column kanban that can truly execute each task through the DSH agent engine.
conversation.view slot, sitting side by side with the built-in Chat (chat) and Trajectory (trajectory) tabs (same mechanism those tabs use).Backlog / In Progress / Done columns, grouped by an arbitrary task group name; group headers collapse/expand all cards underneath.id, title, group, Markdown description, workDir, files[] and status.workDir, sends the card description as a queued prompt, and the agent really does the work.localStorage, key dsh-task-board:v1).--dsw-*), auto light/dark.A DSH "client plugin" is a single npm package with two halves:
| Half | File | Role |
|---|---|---|
| Host half | lib/index.js | A Cordis plugin the Loader mounts in Node — a no-op for a pure-UI plugin |
| Browser half | lib/client.js | Registered into the Web GUI as { inject: [...], apply(ctx) } |
package.json carries the two declarations the harness looks for:
"dsh": {
"client": { // browser-side declaration (platform MUST be "web")
"platform": "web",
"inject": [ /* client packages this module depends on in the boot graph */ ]
},
"bundle": { // profile-bundle declaration (provides a Loader patch)
"patch": "./cordis.patch.yml"
}
}
Inside apply(ctx), the plugin registers a conversation.view entry:
ctx.slots.inject('conversation.view', () =>
ctx.slots.register({
name: 'conversation.view',
id: 'taskboard',
order: 20, // chat = 0, trajectory = 10, taskboard = 20
locale: 'taskboard',
label: () => t('view.task'),
}, TaskBoardView),
)
When a card is dropped into In Progress, the browser half runs the real execution pipeline:
ctx.sessions.create({ cwd: task.workDir }) — the host accepts any absolute cwd; a new session is created per run (its sessionId is stored on the card so you can reopen and inspect it later).binding = ctx.sessions.binding(sessionId) → binding.session.open().session.prompt([{ type: 'text', text: taskDescription }], 'queue').binding.eventSource and stream assistant/live-chunk text back onto the card.user/message → turn/end, running === false, the queue and pending submissions are empty → mark completed with the last assistant/message text.promptError, lastAgentError) or an 8-hour timeout send the card back to Backlog with the error shown.Event-window note: session window entries are shaped
{ type: 'event' | 'transient', event: { type, seq, time, data } }— the event kind lives on the innereventobject.
The plugin targets the desktop profile that runs your GUI.
Run inside a DSH terminal:
dsh plugin --profile desktop add <absolute/path/to/dsh-task-board>
Because the package declares dsh.bundle, the CLI appends it to dsh.profile.bundles in ~/.dsh/profiles/desktop/package.json and installs it as a direct dependency.
~/.dsh/profiles/desktop/package.json:
dependencies (a file: spec pointing at the absolute path);"dsh-task-board" to dsh.profile.bundles.pnpm install inside the profile directory.Never hand-edit
cordis.yml— it is rewritten on every launch. Usecordis.patch.ymlor the flows above.
Restart DSH Desktop (bundle-list changes are never hot-applied). After restart, open or create a conversation: the header tab strip (which already shows Chat / Trajectory) will now also show Tasks.
The tab only appears while a conversation is open — that is how the official
conversation.viewmechanism works, not a limitation of this plugin.
| Acceptance item | How to check |
|---|---|
| Tasks tab appears | Open any conversation → tab strip shows Tasks after Chat / Trajectory |
| Create a card with group & files | ＋ New Task → fill title / group / description / workdir / files (one per line) → card appears in Backlog, grouped |
| Drag triggers a real run | Drag card into In Progress → running indicator + streaming output; console logs [dsh-task-board]; a new session shows up in the session list |
| Auto-flow on completion | Turn ends & session idles → card moves to Done with a result summary |
| Re-run | Drag a Done card back into In Progress |
| Group collapse | Click a group header to collapse/expand its cards |
| Persistence | Reload the page — tasks are still there |
Failure path: a rejected prompt, agent error, or 8 h timeout returns the card to Backlog with a ⚠ message; drag it in again to retry.
node scripts/build.mjs # rebuild lib/client.js from src/client.tsx
node scripts/build.mjs --watch # rebuild on changes (for client HMR)
~/.dsh/profiles/node_modules/typescript) via transpileModule (syntax transpilation only, no type-checking, no network). Override with the DSH_TS_LIB env var if needed.require() platform seed modules (React, @deepseek-ai/cordis, …). This plugin therefore ships zero third-party runtime dependencies; type annotations in the source are for readers only.src/client.tsx and rebuilding rewrites lib/client.js; the always-on client HMR reloads that plugin in place (plugin React state is lost, sessions/runtime survive). Manifest changes still need a restart.dsh-task-board/
├─ package.json # dsh.client (web) + dsh.bundle (patch) declarations
├─ cordis.patch.yml # bundle patch: inserts this plugin as a Loader row
├─ tsconfig.json # editor/type-reading only; build does not use it
├─ lib/
│ ├─ index.js # host half (no-op Cordis plugin for the Loader)
│ └─ client.js # browser half (BUILT artifact — edit src/, then rebuild)
├─ src/
│ └─ client.tsx # browser-half source: kanban UI, drag & drop, runner
└─ scripts/
└─ build.mjs # TSX → CJS + ModuleLoader registration shell → lib/client.js
file: dependency install is a copy, after changing src/client.tsx + rebuilding you must refresh the profile copy (pnpm install may say “Already up to date” — copy lib/client.js over manually, or use pnpm link for a live dev loop).workDir: session.create({ cwd }) accepts any absolute path, but whether the host fs/sandbox permits an unregistered directory depends on host configuration — register the directory as a workspace first if it gets blocked.Built against DSH Desktop 2.0.5 internals (@deepseek-ai/dsh-* 0.1.2-rc.1) and verified on a live desktop profile. Internal APIs may change across DSH versions.
MIT