dsh-global-todo
DeepSeek Harness 的全局跨会话待办：由人和 Agent 共同维护的一份清单，记录创建时间，支持附加文档和链接，并可一键交接给 Agent 会话。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:LUgABeEEE/dsh-global-todo#3c0a8dae61cafbed3b9a9630fb3be115a89e99d3
Global Todo 以 dsh-global-todo 发布，当前版本为 0.3.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
One todo list for the whole DeepSeek Harness, owned by you and written by your agent too.
Every entry records when it was added, carries a description, can attach any number of documents and addresses, and can be handed to an agent session with one click — so "continue this" is a button, not a paragraph of context you retype.
DSH's built-in todo_write belongs to one agent session: whole-list replacement, three
states, and a plan that disappears when the session does. The community plugins that fix
that split into two camps — the ones that dispatch work to agents (auto-resume, bound
sessions) and the ones that accept real document attachments. This plugin does both, on
one record:
built-in todo_write | dsh-global-todo | |
|---|---|---|
| Owner | one agent session | you — across sessions and workspaces |
| Writing | whole-list replacement | per-field, human and agent |
| When it was added | not tracked | createdAt, immutable, shown everywhere |
| Context | title + state | description + documents and addresses |
| Hand-off | — | one click: reuse the bound conversation or open a session |
| Storage | session event log | one JSON file you can cat, edit, diff and back up |
The panel: count chips, grouped list, urgent rows marked
One row opened: inline editing, attachments with 打开 / 复制路径, activity
These are produced by npm run screenshots (which chains npm run preview): the real client
half is rendered to static HTML with no Host and no dependencies, then photographed at 1280×720
into docs/screenshots/. Playwright is not a dependency — the tool borrows the copy a DSH
profile already installed, or whatever DSH_PLAYWRIGHT points at.
0.2.x (developed and verified against 0.2.0-rc.2)>= 22.19.0 (the Web profile's own requirement)@deepseek-ai/*.# from npm
dsh plugin --profile web add dsh-global-todo
# or from a checkout, which is also the development path
dsh plugin --profile web add /absolute/path/to/dsh-global-todo
The plugin is a Loader row, not a hot-loaded script: restart the host (dsh web)
after installing, then refresh the page. A "待办 / Todos" entry appears in the sidebar.
To roll back:
dsh plugin --profile web remove dsh-global-todo
Your list is not touched by install or uninstall: it lives outside the plugin, at
$DSH_HOME/global-todo/todos.json.
added <time> (<age>) with the exact timestamp on hover, the priority,
the due time, the tags, the attachment count, and which side created the entry./ focuses search, n focuses the new-todo field, Esc collapses the
open detail. Row actions appear on hover or keyboard focus.--trusted-host); the plugin's own loopback check is only the fallback for a
Host without that service. /health reports fence so you can see which one is in force./health. Each conversation's group also carries an Exempt button: it takes that
conversation's whole working directory out of automatic collect (click again to undo). That
is for conversations a machine drives — a chat companion's room — whose session is recreated with
a new id when it restarts, so the exemption is keyed on the directory rather than on one
conversation and cannot quietly stop applying.| Tool | Purpose |
|---|---|
global_todo_add | Record an item — description, attachments, tags, priority, due time |
global_todo_note | Append a progress note — where you are, what blocks you, who must decide |
global_todo_capture | Record a batch: for 「抓一下待办」 or a turn that produced several follow-ups; each entry is validated on its own |
global_todo_list | Query by state, tag or text; every row carries its creation time |
global_todo_get | Read one item in full, including attachments and the last hand-off |
global_todo_update | Change any field of one item; "" clears, [] empties |
global_todo_link | Attach or detach documents and addresses |
global_todo_done | Mark done, back to open, or in progress |
global_todo_reopen | Put a wrongly finished item back (done / cancelled → open); refuses anything else, and the trail records it as the agent |
global_todo_remove | Delete permanently (done items should be marked, not deleted) |
The test suite uses doubles; npm run check:live checks the wired Host instead —
the routes the panel actually calls, the list it actually reads, and a record that survives
delete-then-undo. It creates a temporary record, compares every field after the round trip
(id, creation time, attachments, tags, level, due time, description), asserts that bound
records carry sessionAlive/sessionDir, and removes its temporary record even when it
fails. It needs a running Host, so it is not part of verify.
A guidance section is injected into the system prompt (turn it off with guidance: false).
It states both sides of the policy, because a prompt that only says "remember things"
produces noise, and a noisy list is worse than an empty one:
global_todo_capture and answers with a summary.The boundary: it records, it never starts work. The list belongs to the human, and starting a task stays a human decision (see the non-goals in ROADMAP).
The panel talks to the host over these routes. They are fenced by the host connection fence when that service is present, and by a strict loopback check otherwise.
| Method | Path | Body / query |
|---|---|---|
| GET | /api/global-todo/list | status, query, tag, sort, limit |
| GET | /api/global-todo/get | id |
| GET | /api/global-todo/export | — (the store's own JSON document, for backup or migration) |
| POST | /api/global-todo/import | { doc, mode?: replace|merge } — replace is an exact round trip, merge updates by id and appends (what the panel sends) |
| POST | /api/global-todo/capture | { sessionId? } — ask the current conversation to collect its follow-ups |
| GET | /api/global-todo/health | — (store location, counts, dispatch capabilities, plus tool registration and whether the completion watcher attached — both fail quietly, so both are reported — and metrics: dispatch success rate, agent tool calls, list growth) |
| POST | /api/global-todo/create | { title, description?, links?, tags?, priority?, dueAt? } |
| POST | /api/global-todo/update | { id, ...fields, by?: human|agent } |
| POST | /api/global-todo/status | { id, status, by?: human|agent } |
| POST | /api/global-todo/remove | { id } |
| POST | /api/global-todo/restore | { todo } — put a removed record back verbatim (undo) |
| POST | /api/global-todo/link | { id, add?: [...], remove?: [value | index] } |
| POST | /api/global-todo/dispatch | { id, mode?: auto|bound|new|current, sessionId?, dir? } |
by on /update and /status says whose write this is: omitted (what the panel sends) it is
the person at the keyboard, and a script acting for the agent says by: 'agent' rather than
being filed as a human. Anything else is a 400 — a provenance field that silently absorbs a
typo is worse than no field at all.
Errors are typed: 400 for a rejected value, 404 for an unknown id, 413 for an
oversized body, 403 for a request that fails the fence, 502 when a hand-off cannot
reach the agents service. The body is always { ok, ... } with a machine reason.
$DSH_HOME/global-todo/todos.json, or any absolute path you set:
# the profile's cordis.patch.yml
- id: global-todo
config:
storePath: /home/me/notes/global-todos.json # a synced or versioned folder
dispatchDir: /home/me/projects/thing # default cwd for a new session
requireExistingFiles: true # refuse a document that is not there yet
The file is the artifact: plain JSON, one record per todo, written through a temp file and
rename(), with a write lock that serializes the human's and the agent's edits. A damaged
file is reported (store-corrupt) rather than silently reset, and a single mangled record
is skipped instead of taking the list down. Back it up by copying it.
Attachments are references, not uploads. A document is an absolute path that stays where it is; an address is a URL. Nothing is copied into plugin storage, so a document stays editable and diffable, the list stays small, and a dispatched agent opens the very same path with its own tools. URLs carrying credentials are refused, because the list, the audit trail and every prompt would otherwise keep a copy of the secret.
Creation time is first-class. createdAt is set once and never rewritten. The panel
shows it, the tools return it as both epoch and ISO, and the dispatch prompt includes it,
because "when did this land on my plate" is half of what a global todo is for.
One write path. The panel and the tools both call the same service functions, so a validation rule, an audit entry or the write lock cannot exist on one side only.
A failed hand-off is louder than a successful one. Success and failure are both recorded on the todo, and the panel shows the failure with its reason. A dispatch that silently did nothing is worse than one that never happened.
Optional services degrade, they do not crash. webServer, tools, agents,
agentPresets, workspaceRegistry and agentDefaultModel are all reached through
ctx.inject or a guarded ctx.get. A lean composition loses exactly that surface.
See docs/DESIGN.md for the data model and the rejected alternatives, and docs/ROADMAP.md for what could come next.
npm run check # parse every file, assert the shipping shape, and — when a DSH
# profile is present — validate every tool schema against the
# Host's own validator
npm test # 100+ unit, contract and bundle tests, zero dependencies
npm run verify # both
There is no build step. The host half is plain ESM under lib/; the client half is a
classic script that registers itself with window.__ModuleLoader__, so no bundler,
TypeScript toolchain or CI artifact is involved. lib/client.js edits take effect on a
page refresh; host-half edits need a host restart.
npm run preview # render the panel to preview/panel.html (+ detail and selection variants)
npm run screenshots # re-photograph those previews into docs/screenshots/, 1280×720
The three PNGs under docs/screenshots/ ship with the package and are embedded in both
READMEs, so re-run npm run screenshots whenever the panel UI changes.
lib/
index.js host entry: store + service + dispatcher + the three surfaces
store.js one JSON file: atomic writes, serialized updates, tolerant loads
model.js the todo entity: validation, patches, status, attachments, activity
links.js attachment rules (pure: no filesystem access)
service.js the single write path, filters and sorting
routes.js the HTTP surface for the panel
tools.js the ten agent tools
dispatch.js handing a todo to an agent session
errors.js typed failures with stable machine codes
client.js the browser half (panel + sidebar entry)
test/ unit, service, tool, route, dispatch, bundle and manifest tests
tools/ preview.mjs — render the panel to static HTML without a Host
screenshot.mjs — photograph those previews (borrows the profile's Playwright)
docs/ DESIGN.md (data model and rejected alternatives), ROADMAP.md
Contributions are welcome — read CONTRIBUTING.md first.
The HTTP surface is local-only, the list is a local file, and no credential is ever stored. Please report vulnerabilities as described in SECURITY.md.
MIT © 2026 LUgABeEEE
Collect选择, tick a few todos, and one click sends each one to the
conversation that wrote it, else to a same-workspace conversation, else to a target you pick.
That is an attempt order: an unloadable target means the next one is tried. Anything with
nowhere to go comes back with a picker rather than being sent somewhere unchosen, and one
failure does not abort the batch.tag:release (or #ops), is:overdue, is:active, has:link,
has:note, level:p0, plus free words combined with AND (which also match note text). A
search without a colon behaves exactly as it always did.＋ new conversation · <workspace>), and a named workspace wins over the
inherited one. The working directory only decides when neither is known.updatedAt). Conversations sharing a title get a short id
suffix, and a target that is no longer listed (archived since it was chosen) is shown as
(archived) instead of appearing as a different conversation.交给：[ conversation ▾ ], listing your
conversations: whichever you choose is sent with authoritative: true and the Host honours
it verbatim, with no inference on top. The list marks the conversation the Host would have
chosen on its own, 自动 restores that behaviour, and ＋ a new conversation starts a fresh
context. A choice is remembered, and changing it is one click in the same control — what you
see is what happens.current: the conversation you last wrote in (read from the session log,
keeping only source.kind === 'user' messages — the plugin's own injected hand-off
messages are excluded, or each dispatch would drag the next one to its own target; the id
is also kept next to the data so a restart does not forget it). auto prefers the
conversation this todo already owns, then the current one, and only then opens a fresh
session; new always opens one; bound insists on the bound conversation and says why
if it is gone. When nothing usable can be resolved the hand-off fails with a reason
instead of quietly opening another conversation.conversation / time / level and defaults to
conversation: everything one agent conversation submitted collapses into a single
entry that says how many it holds, so a few 「抓一下待办」 runs do not turn the list into a
wall of rows. A conversation with one item shows that row directly; items with no source
conversation (added in the panel) sit under 手动添加. time is the original
overdue / today / soon / later / no-due buckets, level groups by priority.P0 urgent / P1 high / P2 normal (default) / P3 low, with a badge on the
row. Records written before levels existed keep their high/normal/low, so nothing needed a
migration. A conversation group shows the highest level it holds, and a green dot marks a
group with a conversation still running.global_todo_capture" into the conversation you are in, so a chat turns
into todos without typing them out. The prompt states what not to record as well
(session plans, small talk, finished work) — a capture instruction without that ceiling
only produces noise.global_todo_done with
summary and artifacts remains the primary path; the watcher is the safety net.