DSH-taskboard

DSH Taskboard

English | 简体中文

Native, local project task management for DeepSeek Harness. SQLite is the sole task authority. Harness Agent Sessions, Goals, Workspaces, tools, permissions, and the Web Client remain the execution and conversation owners.

This README is written so a human or another coding agent can install the plugin into a live Harness profile, verify it, and start using it without guessing.

Package: @shengsheng/dsh-taskboard Repository: https://github.com/shengsheng90/DSH-taskboard License: Apache-2.0 Host version policy: DSH runtime peers use * (no version gate). Installation/loading is tested against 0.1.6-alpha.1, 0.1.7-rc.1/rc.2, 0.2.0-rc.1/rc.2, and 0.2.1-rc.2. This verifies installation and module loading; GUI operations and model execution still need checking after a Host upgrade.

If you are an installing agent, jump to Install into DeepSeek Harness and follow every step in order. Git, npm, and release tarballs carry prebuilt Host/Client artifacts. Installation requires neither a TypeScript build nor a Harness source checkout. What you get

After a successful install, Harness gains: A Taskboard sidebar button and a native overlay page (not an iframe, not a second chat runtime) Local SQLite projects, tasks, comments, relations, attachments, workflows, and automation Stable readable keys such as DSH-42 plus opaque ids and optimistic versions Seven statuses: backlog → todo → in_progress → in_review → done, plus blocked and canceled In-process Agent tools taskboard_* (no accept / no generic status mutation) Headless JSON CLI dsh-taskboard Packaged Skill manage-taskboard

Agents can submit verified work to in_review. Only an authenticated human UI or CLI operation can accept it as done.

Further design docs: Architecture, Security and recovery, CLI reference, Acceptance audit. Attribution shipped to package consumers is in THIRD_PARTY_NOTICES.md. Requirements Confirm the toolchain before installing:

Install into DeepSeek Harness

Use these constants. Read live values from disk; do not invent a different package name. is whatever this repo's package.json currently declares — read it there rather than copying a number out of this document. After pnpm pack, use the tarball that was actually written.

A longer copy-paste prompt for a Harness-side agent is in docs/install-plugin-prompt.zh.md. The steps below are the normative English procedure. 1. Detect the running Harness

Find the Web listener and its working directory: