Back to directory

dsh-todolist

In a curated listMaintenance: Active

shuxidemosheng/dsh-todolist

Give the DSH agent a richer todo_write_plus tool plus a floating, draggable task panel that follows the current run.

View on GitHubHomepage
$ dsh plugin --profile <your profile> add @shuxidemosheng/dsh-todolist

105

stars

0

forks

JavaScript

Language

NOASSERTION

License

2026-10-03

Created

2026-11-18

Last push

Enhanced fork of DSH's official todo_write: priority labels, full markdown checklist results, and a draggable floating task panel that follows the current session (MIT per the README).

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-20

License

NOASSERTION

01What can it help you accomplish?

  • Keep a prioritized, fully rendered task list inside a DSH session instead of the official one-line counter

    A `todo_write_plus` tool whose results carry high / medium / low priority labels and return the complete markdown checklist to the model

    DSH users driving multi-step work who want the plan written down where the model and the user both see it

  • Watch progress while the agent works, without switching to a side panel or another window

    A self-drawn floating overlay inside the session: expanded / capsule states, current tool line, subagent rows, and the previous round kept dimmed instead of blinking empty

    Users running long sessions in the DSH desktop app who want the plan visible next to the conversation

  • Add the panel to a desktop setup that already runs the official todo_write, without breaking existing sessions

    Side-by-side coexistence: the plugin registers as `todo_write_plus` and reuses the official `todo/write` event type, so logs written by either side stay readable

    Teams whose desktop agent presets already include the built-in todo tool and cannot simply replace it

02How to install into DeepSeek Harness

Prerequisites

  • A `dsh` CLI profile, or the DSH desktop app (the README gives a separate desktop-side command run through `ELECTRON_RUN_AS_NODE`)
  • Node.js ≥ 24 — the README states this requirement for the from-source build path

Installation steps

  1. 01

    CLI profile: `dsh plugin --profile <your profile> add @shuxidemosheng/dsh-todolist` — installing by package name needs no git URL and accepts a version

    $ dsh plugin --profile <your profile> add @shuxidemosheng/dsh-todolist

  2. 02

    Alternatively use the git channel: `dsh plugin --profile <your profile> add https://github.com/shuxidemosheng/dsh-todolist.git` to always pull the latest main

    $ dsh plugin --profile <your profile> add https://github.com/shuxidemosheng/dsh-todolist.git

  3. 03

    Or use the desktop app: Plugins → Add plugin → paste the repository URL or package name — a failed install rolls back automatically (quit the app first, system tray included)

  4. 04

    Restart the client after installing or upgrading

Verify the integration

  • Check the installed version: `grep '"version"' ~/.dsh/profiles/desktop/node_modules/@shuxidemosheng/dsh-todolist/package.json`

03DSH integration and capability boundaries

DSH integrationNative runtime

A native DSH plugin installed with `dsh plugin add`: the host half registers an enhanced todo tool, the client half draws a floating task panel inside the session

  • Enhanced todo tool (`todo_write_plus`)

    todo items with an optional `priority` of `high` / `medium` / `low`→the full markdown checklist returned to the model, plus a `todo/write` event in the session log

    input is normalized instead of rejected since 0.7.3: blank `content` dropped, duplicates suffixed, extra in_progress items downgraded to pendingthe adjustment is reported back to the model in the tool result
  • Floating task panel

    the session's `todos` projection→an expanded view (status dots, strike-through, priority badges, progress count, in-progress marker) that toggles to a capsule view of the same priority chain

    stores the dragged panel position in localStorage under the key `dsh-todo-plus.panelPos` as `{x, y}`
  • Current action and subagent status

    tool calls already emitted in the session node stream, and the `subagentCatalog` / `subagentTiming` projections→a live current-tool line between checklist writes, and a collapsible subagent row with each name, state and elapsed time

  • Round-to-round continuity

    the previous round's checklist→the old list stays on screen and is dimmed with a "previous round" label until a new write replaces it

  • Configurable discipline and tool name

    `allowParallelInProgress` and `toolName` in the bundle config of `cordis.patch.yml`→single-active-task discipline by default; on CLI profiles the plugin can take over the plain `todo_write` name once the official `tool-todo` row is disabled

04Who is it for? When not to use it?

Good for

  • DSH users driving multi-step work who want the plan written down where the model and the user both see it
  • Users running long sessions in the DSH desktop app who want the plan visible next to the conversation
  • Teams whose desktop agent presets already include the built-in todo tool and cannot simply replace it

Not for

  • Since dsh 0.2.1-rc.2 the host validates a plugin's compatibility declaration at startup. Releases up to 0.7.3 pinned the peer to `0.2.0-rc.2` and are refused there; 0.7.4+ declares `engines.dsh: ">=0.2.0-rc.2 <0.3.0"` and loads again.
  • On dsh 0.2.2-rc.1 and later every registrant of the same projection key must declare the same `stateVersion` and `summary`. The official `tool-todo` writes `summary: false`, so versions up to 0.7.4 threw on `register()` and session creation failed when both coexisted; 0.7.5 aligns with the official definition.
  • Installing by bare package name goes through npm, and dsh's built-in `minimumReleaseAge` supply-chain policy resolves it to the last release old enough to clear a multi-day cooldown — a fresh install or upgrade can silently land on an older version while the plugin card still shows the latest registry number. Pin the version when you need the newest release.

05Compatibility, maintenance and safety notes

  • Since dsh 0.2.1-rc.2 the host validates a plugin's compatibility declaration at startup. Releases up to 0.7.3 pinned the peer to `0.2.0-rc.2` and are refused there; 0.7.4+ declares `engines.dsh: ">=0.2.0-rc.2 <0.3.0"` and loads again.
  • On dsh 0.2.2-rc.1 and later every registrant of the same projection key must declare the same `stateVersion` and `summary`. The official `tool-todo` writes `summary: false`, so versions up to 0.7.4 threw on `register()` and session creation failed when both coexisted; 0.7.5 aligns with the official definition.
  • Installing by bare package name goes through npm, and dsh's built-in `minimumReleaseAge` supply-chain policy resolves it to the last release old enough to clear a multi-day cooldown — a fresh install or upgrade can silently land on an older version while the plugin card still shows the latest registry number. Pin the version when you need the newest release.
  • The panel only mirrors the `todos` projection. If the model reports progress in prose without calling the tool, the panel stays on the old step — the plugin is a display layer and will not invent progress. It also only appears inside the session view, by design.
2026-10-032026-11-17v0.8.0

README states MIT while GitHub reports NOASSERTION · actively maintained (latest release v0.8.0, 2026-11-18)

06Frequently asked questions

How do I install dsh-todolist into DeepSeek Harness?

On a CLI profile run `dsh plugin --profile <your profile> add @shuxidemosheng/dsh-todolist`; git and desktop paths are also documented (add the repo URL in the desktop Plugins page, or install from a `.tgz` you built). Restart the client afterwards. Because dsh's `minimumReleaseAge` policy resolves bare package names to an older release during the cooldown window, pin a version such as `@shuxidemosheng/dsh-todolist@0.8.0` if you need the latest.

Will it conflict with the official todo_write tool?

No. On the desktop the plugin registers as `todo_write_plus` next to the official `todo_write`, reuses the official `todo/write` event type so both sides can read each other's logs, and steps aside with a log line if the tool name is already taken — the entry still activates, so the agent preset audit does not fail. Desktop agent presets cannot disable the official `tool-todo` row, so coexistence is the default there.

The panel is stuck on a step that is already finished — why?

The panel and the official inline task bar read the same `todos` projection, so if both stop at the same step, no later checklist write was accepted. Check the version (a cooldown install may be old), then look at the `todo_write_plus` calls in the Trajectory tab: a red error means a rejected write (0.7.2 and earlier hard-rejected multiple in_progress items), and no further call means the model reported progress in text instead of calling the tool. Since 0.7.3 writes are normalized rather than rejected, so the panel no longer freezes permanently.

Does the plugin send anything over the network or touch my files?

No. Both halves are self-contained with no runtime npm dependencies; the client half makes no network request and uses no `eval` / `innerHTML`, and its only local write is the panel position `{x, y}` in localStorage under `dsh-todo-plus.panelPos`. The host half registers the tool and the projection and appends events to the session log — it does not touch the filesystem or the network.

Which dsh versions are supported?

0.7.4 and later declare `engines.dsh: ">=0.2.0-rc.2 <0.3.0"`, so 0.2.x release-candidate upgrades are not blocked; 0.7.5 additionally aligns the projection registration with the official `summary: false` required by dsh 0.2.2-rc.1. Versions up to 0.7.3 pinned the peer to `0.2.0-rc.2` and are refused on 0.2.1-rc.2 or later.

08Data and sources

  • Author-claimedgithub.com9fb01d20f250…

    **DeepSeek Harness 任务清单插件 —— 官方 [`todo_write`](https://github.com/deepseek-ai/deepseek-harness) 的增强 fork**

  • Author-claimedgithub.com9fb01d20f250…

    - **模型侧**:注册增强版任务清单工具。是否建清单由模型根据任务复杂度自主判断(多步骤任务通常会建)

  • Author-claimedgithub.com9fb01d20f250…

    - 本插件在桌面端注册为 **`todo_write_plus`**,与官方 `todo_write` 并存,零冲突

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.