dsh-trilogy
Per-project memory for DeepSeek Harness. Three Markdown files per workspace — PROJECT.md, DECISIONS.md and SESSIONS.md — are auto-created on the first step of any session in that workspace, re-read from disk and re-injected only when they change (and re-injected if compaction dropped them), and written back by classification through a memory_checkpoint tool, with a bounded end-of-turn nudge when a turn did work but recorded nothing. memory_read and memory_search read the live log and the archive, the latter over a zero-dependency BM25 index. The session log is capped at 200 entries with the overflow moved to SESSIONS-archive.md — never injected, but visible, readable and searchable, and restorable one entry at a time. Settings page: a workspace list with a path filter, read-only tabs for the three memory files plus the archive, reload, export/import of one workspace's memory as a JSON bundle, a two-step clear, a panel that rewrites or removes the AGENTS.md instruction block, and a PROJECT.md staleness reminder. A composer status chip shows that workspace's sync state and creates the files on click. Zero dependencies — no vector store, no embeddings, and no model calls.
On this page
Review info: no independent structural review record is currently matched.
Community signals
Category
Memory
GitHub stars
1
npm downloads
—
Discovery registry added
2026-09-18
Review information
Scanner status
No review data
Review mode
No review data
Last checked
No review data
Build approval required
No review data
Lifecycle scripts
No review data
Runtime artifacts committed
No review data
Documented profiles
No review data
Why this site does not provide the install command
A third-party DSH plugin is executable local code. Even when structural review evidence exists, registry data, stars and metadata cannot prove the code is non-malicious. Read the current author repository and perform your own review in a disposable environment.
Install and usage source
This site links to the author's source, npm page and community registry instead of redistributing commands. A plugin may add Web UI, Settings, agent tools or background capabilities; follow the author README for the actual entry point.
Minimum checks before install
- Confirm package.json, the bundle patch and README belong to the same author repository.
- Inspect preinstall/install/postinstall/prepare, child_process, shell, filesystem, network calls and credential access.
- First install into a disposable profile/workspace without production credentials or an important repository.
- If pnpm asks for allowBuilds/build approval, treat it as permission to execute third-party code during installation; do not approve mechanically.
- For reproducibility, pin an exact npm version or Git commit yourself instead of depending on main/latest.
“Third-party” only means the plugin is not an official DeepSeek plugin. Structural checks improve transparency but cannot prove business logic is non-malicious or fully audit dependencies, future updates or runtime behavior.