dsh-octop-memory

Q: Does it collide with dsh-mnemon?

dsh-octop-memory is the one to keep here: 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: What happens when dsh upgrades?

Nothing declares a version window for dsh-octop-memory: dsh --version tells you what you are running, and no check will tell you whether dsh-octop-memory matches it.

Recalls shared memory before each turn and writes new facts back after.

Version 0.1.7 of dsh-octop-memory, last published 2026-11-13; the install command and the range come from its own manifest.

Install

dsh plugin add dsh-octop-memory 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-octop-memory

Compatibility

dsh-octop-memory ships no engines.dsh entry, so nothing checks it against your CLI version at boot. Read the npm page before installing.

If two plugins fight

Injects recalled memory before each turn. dsh-mnemon builds context views for the same slot, so both writing means the model gets two context blocks that can contradict each other.

Who made it

Author: ArvinQi. Repository: https://github.com/ArvinQi/dsh-octop-memory. Package page: https://www.npmjs.com/package/dsh-octop-memory.

After install

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

Files it touches

No storage peer appears in the manifest of dsh-octop-memory, 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-octop-memory is the mirror command, dsh plugin --profile web remove dsh-octop-memory. 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-mnemon?

dsh-octop-memory is the one to keep here: 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.

What happens when dsh upgrades?

Nothing declares a version window for dsh-octop-memory: dsh --version tells you what you are running, and no check will tell you whether dsh-octop-memory matches it.