seek://plugins/dsh-project-manager
dsh-project-manager — a Project Board Linking Memory, Repos and Sessions
#kanban #project-management #memory #sessions #workflow
TL;DR
Per its README, dsh-project-manager adds a project board to DSH: card groups hold parent projects, cards drag through editable stages, and each card links landfill STATEs, repos and sessions — card-opened sessions inherit the group ∪ card memory each turn. A Project zone nests groups as sub-workspaces; the agent works the board via its board tools. Zero config; landfill projects scan ~/.ai.
dsh-project-manager bolts a project board onto DeepSeek Harness where the card — not the workspace — is the unit of work: stages advance by drag, each card links landfill-project memory, mounted repos and sessions, and a session opened from a card starts with the project's status and next_action already in context. A sidebar Project zone nests card groups as sub-workspaces with live session counts, and the agent drives the board itself through its card/repo/phase/task tools. Per its README the deliberate difference from existing boards is skipping generic todos for the project → memory → repos → sessions chain; it needs the dsh web UI, was tested against 0.2.0-rc.2, and runs zero-config with landfill projects scanned read-only from ~/.ai.
Facts
- install
- dsh plugin add dsh-project-manager
- license
- MIT
- note
- 据其 README：需 dsh web 界面（CLI 的 dsh web 或 DSH Desktop）；实测 dsh 0.2.0-rc.2（0.11.0）；侧栏计数、层级与「+」依赖 dsh 工作区列表结构，dsh 改版后自动不显示，看板不受影响。npm latest 0.11.0（本站 2026-10-13 探测）。
Key points
- Per its README, the board is project-shaped: one swim lane per card group, with stage names, count and order editable; cards drag within a stage (Alt+↑/↓ from the keyboard) or into another stage to advance, and groups reorder by a header handle; every stage keeps an always-visible add-card row (Enter adds and keeps typing), with bulk import from landfill projects (one STATE → one auto-linked card) as the alternative; archived cards live in a collapsed tray with restore-to-stage that never touches their sessions
- Sessions and memory interlock per its README: sessions created from or linked to a card get the deduplicated group ∪ card landfill memory injected every turn (one-line status, next_action, STATE path), skipping STATEs the session already read at link time; card materials — free-text notes (truncated past 16KB with a note), links and absolute file paths — ride along too; a strip above the composer reports N projects auto-read and M skipped as already read, collapsed by default
- The sidebar Project zone: the plugin pins a 项目区 (Project zone) workspace atop the workspace list with each card group as a sub-workspace (nested when the view is set to workspace tree); the group row shows its unarchived-session count (grey at 0, updating live); entering a session from the board auto-expands and scrolls to its group; the + button opens a card picker before the new-session dialog; when a card has no linked landfill project but its title contains the name of some landfill project, an explicit Link button (the README's one-click 关联) appears — never a silent auto-link
- Agent tools and the stated difference: the tools card_manage / repo_manage / phase_move / task_manage — and inside a project session, omitting card targets the session's own card; the README's difference section says most board plugins track per-workspace todos, while this plugin does no generic todos at all, only the project → landfill memory → repos → sessions chain: the card is the project, and sessions inherit its context
- Compatibility per its README: tested on dsh CLI 0.2.0-rc.2 (plugin 0.11.0) and DSH Desktop 2.0.17 (bundled 0.2.0-rc.2); per its README, 0.1.5-rc.1 passed back at plugin 0.4.0 and is untested since 0.5.0; peerDependencies declare compatible ranges for cordis, dsh-tools, dsh-client-ui-slots and schemastery, with other in-range versions not individually tested; zero config — landfill projects scan ~/.ai read-only by default
FAQ
How is this different from per-workspace todo boards?
Per its README's difference section: most board plugins track todos per workspace; this one skips generic todos entirely and builds only the project → landfill memory → repos → sessions chain — the card is the project, each card links landfill STATEs, mounted repos and bound sessions, and sessions opened from it inherit the project context automatically.
What are landfill projects and how do I link them?
Per its README, landfill projects are the STATEs persisted by /landfill-project: a board card links them via its linked-projects picker (titles only by default, expandable to project name, updated date, one-line status and next_action); when a card has none linked but its title contains the name of some landfill project, the new-session dialog and the memory strip show an explicit Link button — no silent auto-linking; landfill projects scan ~/.ai read-only by default.
After a dsh upgrade the sidebar counts and indentation vanished — is it broken?
Per its README: the Project zone counts, indentation and the + takeover depend on the markup of dsh's workspace list; if a future dsh changes it, those three simply stop showing — the board and sessions keep working.
Official references
- docsRepository ↗
- docsREADME (English) ↗
- docs中文 README ↗
- docsnpm package page ↗
Embed this badge
[](https://dshseek.com/plugins/dsh-project-manager/)Shows the month this entry was last human-verified — it changes only on re-verification, never with daily stats.