dsh-memory-delta
Layered cross-session memory for DSH that pushes only what changed. The first round injects every active entry, later rounds push only added / updated / removed ones, and nothing at all is injected when nothing changed. Facts and decisions carry semantic keys (one active truth per key), the model may only write to an inbox that a human promotes, an entry can carry a review date that raises a one-time reminder when it comes due, search is relevance-ranked with Chinese matched by bigram, and a sidebar tab tells the lifecycle story instead of just listing files — entries are grouped into awaiting confirmation / in use / archived, viewable by type, tag or date, and the tab can promote a candidate, withdraw or archive a standing entry, restore an archived one and delete a candidate, alongside the global and workspace instruction files and the current injection size. A zero-dependency CLI ships with it, so the store is usable without DSH.
On this page
Review info: no independent structural review record is currently matched.
Community signals
Category
Memory
GitHub stars
0
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.