flymysql/dsh-memory
Cross-session memory vault: remember / recall / forget tools, per-turn prompt injection, and a settings-page entry browser.
dsh-memory-vault gives DeepSeek Harness agents a persistent cross-session second brain: three model tools (memory_remember / memory_recall / memory_forget) plus per-turn prompt injection of the most recent entries, so every session starts aware of stored facts, preferences, decisions and project notes. Records are durable in a storage-domain unit, and a '记忆库 / Memory' page in Settings lets you browse, add and delete entries directly.
Install
dsh plugin --profile web add dsh-memory-vaultnpm dsh-memory-vault 0.1.5 verified 2026-09-03 (repository field → github.com/flymysql/dsh-memory; README EN primary with a zh usage example). Install: dsh plugin --profile web add dsh-memory-vault (the dsh.bundle manifest wires the dsh-memory row automatically), or npm install dsh-memory-vault plus a manual cordis.yml row.
Compatibility
DSH web profile; records live in a harness storage domain (dsh_memory unit, json backend by default; unit names snake_case per UNIT_NAME_RE).
Details
- Repo: flymysql/dsh-memory
- Category: Memory
- Stars: 0
- Version: npm dsh-memory-vault 0.1.5
- Last push: 2026-09-21
- First seen: 2026-08-14
Recent updates
0.1.5 current on npm (verified 2026-09-03).
FAQ
- What survives across sessions?
- Anything written with memory_remember — facts, preferences, decisions, project notes — stored in the dsh_memory storage-domain unit and re-injected into later system-prompt assemblies.
- Can the agent forget?
- Yes — memory_forget removes an entry, and the Settings memory page also supports direct add/delete.
- Is a separate database needed?
- No — storage uses the harness's own storage-domain mechanism with a json backend by default; no external server.
Alternatives
ICCuse/dsh-file-memory · aqsk-BLG/dsh-memory