A DeepSeek Harness plugin and skill that records tasks as a git-committed plain-text ledger in `ledger/`, driven purely by conversation, with a DSH board for in-flight work, weekly trends and closed history.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-15
License
MIT
01What can it help you accomplish?
Carry any kind of work — research, docs, demos, video — as a task on a ledger kept in the workspace instead of in a chat window
A plain-text ledger under `ledger/`: JSON for ownership and status, Markdown for the running narrative, with time and owner attached to every status change
Individuals and teams whose work spans several sessions or days, or gets handed over between people
See in-flight, unclaimed, overdue and stalled tasks plus weekly trends on a board panel inside DSH
A board grouped by owner, with closed-task history aggregated by day / week / month / quarter
People who want to manage the ledger visually without moving the answers to a hosted project-management tool
02How to install into DeepSeek Harness
Prerequisites
- DeepSeek Harness (DSH) — the README names DSH as the project's main form, installed as a DSH plugin
- No account, hosted backend or service marketplace is needed for the ledger itself
Installation steps
- 01
In DSH open the plugin page, click the add-plugin action, enter the package name `dsh-task-ledger` and confirm the install
- 02
Or run `dsh plugin add dsh-task-ledger` in a terminal
$ dsh plugin add dsh-task-ledger
- 03
Or search `dsh-task-ledger` in the DSH plugin marketplace and install it there
Verify the integration
- After installing, the full board is available and the skill is already bundled — no separate skill installation is required
03DSH integration and capability boundaries
Native DSH plugin — added from the DSH plugin page, via `dsh plugin add`, or from the DSH plugin marketplace; it ships the board panel and a built-in skill
Task lifecycle tracking
an explicit instruction in the DSH conversation — create, claim, continue, hand over, close, delete→status changes with time and owner; narrative, closing conclusion and leftovers written into the task body
every state change is written into the `ledger/` directoryLocal plain-text ledger
task notes and status changes→JSON and Markdown committed alongside the repository — readable, diffable and reviewable offline
the ledger is committed together with the repositoryPer-owner sharded ownership
several people sharing one repository→`pool.json` for unclaimed tasks, `owners.json` as the identity index, one `owners/<hash>.json` shard per person
two people advancing their own tasks do not write the same fileBoard with weekly trends and closed history
the ledger files in the workspace→in-flight, unclaimed, overdue and stalled tasks per owner, weekly trends, and closed history aggregated by day / week / month / quarter
04Who is it for? When not to use it?
Good for
- Individuals and teams whose work spans several sessions or days, or gets handed over between people
- People who want to manage the ledger visually without moving the answers to a hosted project-management tool
Not for
- The agent never starts a create, claim, release, close or delete on its own — each needs your explicit instruction, and vague wording such as "it's done" makes it ask back instead of closing. Status files, history files and worklogs are off-limits to it: it may only write the first five sections of a task body.
- The board currently exists only in the DeepSeek Harness plugin board. Other agents — Claude Code, Cursor, Codex, CodeBuddy, Trae, anything that loads SKILL.md — can install the skill and keep the same ledger, but they get no board.
- Deletion asks you to confirm first and is then permanent — no undo, no restore. Closing is a different operation: it asks for a summary, moves the task into history and leaves it read-only.
05Compatibility, maintenance and safety notes
- The agent never starts a create, claim, release, close or delete on its own — each needs your explicit instruction, and vague wording such as "it's done" makes it ask back instead of closing. Status files, history files and worklogs are off-limits to it: it may only write the first five sections of a task body.
- The board currently exists only in the DeepSeek Harness plugin board. Other agents — Claude Code, Cursor, Codex, CodeBuddy, Trae, anything that loads SKILL.md — can install the skill and keep the same ledger, but they get no board.
- Deletion asks you to confirm first and is then permanent — no undo, no restore. Closing is a different operation: it asks for a summary, moves the task into history and leaves it read-only.
MIT · no tagged release, last push 2026-11-12
06Frequently asked questions
How do I install dsh-task-ledger in DeepSeek Harness?
Any of three routes: on the DSH plugin page click the add-plugin action, enter the package name `dsh-task-ledger` and confirm; run `dsh plugin add dsh-task-ledger` in a terminal; or search `dsh-task-ledger` in the DSH plugin marketplace and install it there. The board and the skill come with the plugin, so no separate skill installation is needed.
What does the plugin change in a DSH session?
It adds the full task board and a built-in skill. You drive it in plain language — new task, claim this one, keep going on X, blocked / park it, release it, close it, cancel it, delete it, what should I do now, what was closed last week — and the agent performs the matching operation and records it in the ledger. Read-only questions such as "what was closed last week" write nothing.
Where does the ledger live, and does any data leave the machine?
Everything stays under `ledger/` in your workspace: `pool.json` for unclaimed tasks, `owners.json` plus per-owner shards, `worklog/<month>/*.md` for task bodies and `history/<month>.md` for closed tasks. It is committed with the repository, works offline, and needs no account, hosted backend or service marketplace. Sharing happens through git push / pull / merge, so the commit history itself becomes the audit trail.
Can I keep the same ledger from Claude Code, Codex or another agent?
Yes — `npx skills add cq-guojia/dsh-task-ledger -g` installs the skill and detects the agent tools already on the machine (Claude Code, Codex, CodeBuddy and others); the same skill installed elsewhere still records the same project ledger. The board, however, currently only exists in the DeepSeek Harness plugin board, so use the DSH plugin when you want the board.
Can a deleted task be restored?
No. Deletion asks you to confirm first and then removes the task permanently — no undo, no restore. Closing is different: it takes a summary, moves the task into history and leaves it read-only.
07Related DSH workflows
dsh-agent-teams
by nanmicoder
AgentTeams 多智能体团队协作插件:自然语言驱动建团队、拉成员、拆任务声明依赖、成员间消息直达,Web 右上角活动面板
dsh-blender-plugin
by sixtysevenlf
Adds tools for Blender scene editing, viewport capture, render profiling, headless work, and verification.
dsh-free-search
by dddmuc
DSH 免费搜索插件,执行联网检索。
dsh-bili-scroll
by c1overzz
Schedules Bilibili discovery, reads subtitles, writes daily reports, and optionally posts a comment tagging you.
08Data and sources
本项目的主形态是 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)(下称 DSH)插件:装好就有完整看板,skill 也已内置,无需另外安装。三种方式任选…
1. **在 DSH 里添加插件** —— 打开插件页,点「添加插件」,输入包名 `dsh-task-ledger`,确认安装。
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-15. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
