dsh-mnemon

Q: Does it collide with dsh-octop-memory?

For dsh-mnemon the recommendation is dsh-octop-memory: dsh-octop-memory writes facts back to disk at the end of the turn, and dsh-mnemon keeps nothing on disk — so when both are installed, only octop-memory is doing that write-back.

Q: Which dsh versions load it, and what happens outside that window?

On >=0.2.0-rc.2 =0.2.1-rc.1 <0.3.0-0 the CLI loads dsh-mnemon; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-mnemon is the per-package override if you accept the risk.

Composable, view-based context: what the model sees is assembled from views you can swap, instead of one growing transcript.

Version 0.5.45 of dsh-mnemon, last published 2026-11-12; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-mnemon writes one dependency line into the profile manifest; pnpm then unpacks it under $DSH_HOME/profiles/<name>/node_modules.

dsh plugin --profile web add dsh-mnemon

Compatibility

engines.dsh in dsh-mnemon declares >=0.2.0-rc.2 <0.2.1-0 || >=0.2.1-rc.1 <0.3.0-0; run dsh --version and compare it, because outside that range the CLI skips the plugin at boot and prints the requirement instead of booting.

If two plugins fight

It builds context views for the slot that dsh-octop-memory also writes recalled facts into. Two context blocks can contradict each other, and the model has no way to rank them.

Who made it

Author: omdsh-dev. Repository: https://github.com/omdsh-dev/dsh-mnemon. Package page: https://www.npmjs.com/package/dsh-mnemon.

After install

It declares @deepseek-ai/cordis as a peer and renders a recalled-memory block in the context sent with every turn; after dsh plugin add dsh-mnemon, dsh --profile web --dump-config lists the row that mounts it.

Files it touches

No storage peer appears in the manifest of dsh-mnemon, so the dependency line in $DSH_HOME/profiles/<name>/package.json is the only file you can point at; the package description names nothing else.

Removing it

Removing dsh-mnemon is the mirror command, dsh plugin --profile web remove dsh-mnemon. Its manifest declares no storage peer, so it writes nothing under $DSH_HOME; removing it leaves no files behind.

Common questions

Does it collide with dsh-octop-memory?

For dsh-mnemon the recommendation is dsh-octop-memory: dsh-octop-memory writes facts back to disk at the end of the turn, and dsh-mnemon keeps nothing on disk — so when both are installed, only octop-memory is doing that write-back.

Which dsh versions load it, and what happens outside that window?

On >=0.2.0-rc.2 <0.2.1-0 || >=0.2.1-rc.1 <0.3.0-0 the CLI loads dsh-mnemon; outside it, boot stops with the requirement instead of running the plugin. dsh plugin allow-version dsh-mnemon is the per-package override if you accept the risk.