dsh-memory

Cross-session long-term memory plugin for DeepSeek Harness (DSH).

中文文档

What it does

Remembers facts, preferences, decisions, and lessons across sessions, so a new session starts with what earlier sessions already learned. Storage lives in $DSH_HOME/storages/memory.json (plain JSON — inspectable, git-friendly). No MCP servers, no vector database, no embedding API, no extra runtime dependencies.

Features

• Cross-session persistence — write in session A, recall in session B; new sessions pick up where old ones left off.
• Relevant memories injected on demand — before each model step, the plugin recalls the most relevant memories for the user's current message (via DSH's agent/pre-step hook) and injects up to injectCount short summaries (default 3). You say "continue the math workbook project" → the project's decisions and lessons appear automatically. No every-turn broadcast of a fixed hot set — you only pay for memories that match what you just said.
• Self-correction loop — when the same error (same code/message) fires repeatedly (lessonizeAfter, default 2), the plugin nudges the agent to write it as an importance-3 lesson; the lesson then auto-injects on related topics, preventing recurrence. User corrections are covered by the memory protocol (write the lesson right away).
• Built-in hygiene — capacity cap with lowest-value eviction first; near-duplicate entries merge instead of piling up (Jaccard ≥ 0.7); optional TTL expiry; deleting importance-3 records requires an explicit confirm.
• Chinese-friendly search — Chinese text is indexed by bigrams plus single-char fallback, English by words, plus exact substring matching. Works without a tokenizer or any ML dependency.
• No unrelated association — weak matches (pure single-char coincidence, filler-only queries like "ok了吗") score zero and are never injected; only substring/tag/bigram-strength matches surface. Saves tokens on short chatter.
• Native integration — uses DSH's own storage domain (ctx.storageDomain), tool registry, and agent lifecycle hooks, so it stays compatible with official releases.

Tools

Tool	Purpose
memory_remember	Store a durable memory (content, kind, tags, scope, importance, optional TTL).
memory_recall	Search memory by keywords; ranks by relevance, importance, recency, past usage.
memory_index	Browse the inventory with kind/tag/scope filters, paginated, title-level.
memory_forget	Delete by id or tags; importance-3 records need confirm: true.
memory_import	Import memories from a JSONL/JSON file through the write chain (not by editing the store file) — safe bulk loading.
memory_reload	Reopen the store from disk after an external edit; merges external changes without a restart.

Kinds: fact | preference | decision | lesson | todo | note. Scopes: user (applies everywhere) or project (this project only).

External-modification protection

The store file is loaded once at startup and written as a whole by the running process (single-writer model). To prevent an in-process write from silently wiping external edits:

• every write checks the file fingerprint first — a mismatch (another process or a script edited it) refuses the write with a clear error instead of overwriting;
• memory_import is the supported way to bulk-load data (goes through the write chain, file and memory stay in sync);
• if you still edit memory.json by hand or copy it in, call memory_reload to merge it back (or restart).

Repeat suppression

Per-step injection skips when the recalled set is unchanged from the previous step, so consecutive messages about the same topic don't re-inject the same block — the「相关记忆」notice appears on topic change, not on every message.

Install & enable

⚠️ Not published to npm yet. Install from a local path with file:.

# 1. add the dependency to your profile
cd ~/.dsh/profiles/<name>
pnpm add dsh-memory@file:/path/to/dsh-memory

# 2. add one row to your agent preset (~/.dsh/.agent-presets/<preset>/agent.cordis.yml)
- id: memory
  name: 'dsh-memory'

# 3. restart DSH — the four tools appear in new sessions

No preset? Mount it on the host plane instead, in ~/.dsh/profiles/<name>/cordis.patch.yml:

- insert:
    - id: memory
      name: 'dsh-memory'

Requires the storage trio already present in the profile (dsh-storage, dsh-storage-json, dsh-storage-domain — the web profile ships with it).

Configuration

All options are optional:

Option	Default	Meaning
maxRecords	400	Capacity cap; lowest-value records evicted first.
maxContentChars	2000	Max content length per record.
injectEnabled	true	Per-step injection of relevant memories (via agent/pre-step).
injectCount	3	Max memories injected per step (0 disables).
injectMaxChars	120	Max chars per injected memory summary.
lessonizeEnabled	true	Auto-nudge to solidify repeated errors as lessons.
lessonizeAfter	2	Same error fingerprint occurrences before nudging.
recencyHalfLifeDays	90	Freshness half-life.
mergeSimilarity	0.7	Near-duplicate merge threshold.
protocolSection	true	Inject the memory protocol prompt section.

Uninstall & troubleshooting

• Uninstall: pnpm remove dsh-memory in the profile, delete the preset/patch row. Data stays in memory.json and is restored on reinstall.
• Tools missing: check the row exists, the dependency is installed, and DSH was restarted.
• Storage errors: the memory plugin needs the storage trio; add it to the patch if your profile lacks it.
• Corrupted memory.json: it is plain JSON — fix it by hand or delete it (deleting resets memory).

Development

npm install && npm run build && npm test   # build + 31 unit tests
npm run smoke                              # real-machine headless round-trip check

License

MIT