What it may solve
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.
Imported third-party catalog description; not a Registry verification conclusion.Sources and public signals
TodayJin/dsh-trilogy
1 stars · — downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19What can currently be confirmed
Active analysis coverage 1/5. Historical chains are retained but do not count toward current coverage.
Not analyzedSource structure
Source structure has not been analyzed.
Not analyzedRepository health
Repository metadata has not been analyzed.
Not analyzednpm release
npm release metadata has not been analyzed.
Analysis completeDSH compatibility
Conclusion: Compatibility verification did not pass: the bounded compatibility check did not pass. Test environment: DSH 0.1.6-alpha.2, web profile.
Analysis completeDependency audit
Conclusion: The dependency audit did not produce a complete report.
Not analyzedFunctional verification
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Analysis completeStatic risk scan
Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.
Analysis completePackage integrity
Conclusion: Package structure or integrity validation did not pass.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.