DSH-taskboard configuration
DeepSeek Harness loads DSH-taskboard into the web profile from $DSH_HOME/profiles/<profile>. The profile composition includes the taskboard configuration layer, with these documented keys:
| Key |
Purpose |
databasePath |
Location of the local SQLite database |
attachmentRoot |
Root location for task attachments |
| Worker-limit keys |
Limits for plugin workers; the README refers to these as worker limits |
The README does not specify default values for these keys. The package requires write access to $DSH_HOME, which defaults to ~/.dsh.
DSH-taskboard commands and tools
DeepSeek Harness exposes the in-process taskboard_* Agent tools and the packaged Skill manage-taskboard. The Agent tools do not provide a generic status mutation or an accept operation. They can submit verified work to in_review; acceptance to done is reserved for an authenticated human through the native UI or the CLI.
The plugin also provides the headless JSON CLI dsh-taskboard. It operates without the Web Client and can be used for taskboard operations from a terminal. The README identifies it as a JSON CLI but does not list its individual subcommands or flags.
DSH-taskboard workflow behaviour
The taskboard supports the statuses backlog, todo, in_progress, in_review, done, blocked and canceled. SQLite is the sole task authority. Tasks also have stable readable keys such as DSH-42, opaque IDs and optimistic versions. DeepSeek Harness remains responsible for Agent Sessions, Goals, Workspaces, tools, permissions and the Web Client.
Requirements and limits
DeepSeek Harness must use the web profile. Node.js ^22.19.0 or >=24.0.0 is required; Node.js 24 is recommended. Repository development uses pnpm 11.15.1, while profile installation uses the pnpm supplied by DeepSeek Harness. Network access is needed to clone the repository and install Node dependencies, and the Harness process must be restartable. Installation and module loading are tested against listed 0.1.x and 0.2.0-rc releases, but GUI operations and model execution still require checking after a Host upgrade.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub