Amengclass/dsh-memory
dsh-memory is a persistent, model-editable memory/notes store for DeepSeek Harness. It gives the agent a first-class way to durably write, fetch and search facts that survive across sessions — something conversation-history search, todo_write, settings and static skill docs do not cover. Tools: memory_set (upsert a fact under a stable key with optional tags), memory_get (read one entry or list all), memory_delete (idempotent), and memory_search (case-insensitive substring over key/value/tags with required-tag filters). Records live in one storage domain (dsh_memory) routed through the built-in ctx.storageDomain seam — not hand-rolled files — so they persist under the deployment's configured backend and emit domain/changed for live UIs. Configuration is schemastery-validated (maxItems 1000, key/value length caps).
Install
dsh plugin --profile web add github:Amengclass/dsh-memoryGitHub/source per README (README EN primary w/ zh edition). npm name dsh-memory is owned by another publisher (bbnopromo) — NOT claimed. Install per README: dsh plugin --profile web add github:Amengclass/dsh-memory (plain ESM JavaScript, no build step, no allowBuilds), or from a checkout: dsh plugin --profile web add ./dsh-memory.
Compatibility
DeepSeek Harness profiles with the storage domain service (@deepseek-ai/dsh-storage-json backend: json by default); runtime peers provided by the harness (dsh-storage-domain, dsh-tools, schemastery, zod).
Details
- Repo: Amengclass/dsh-memory
- Category: Agent Capabilities
- Stars: 0
- Version: GitHub main (Amengclass/dsh-memory; plain-ESM bundle)
- Last push: 2026-08-14
- First seen: 2026-08-14
Recent updates
Differs from memory-MCP servers: no external server or account — a lightweight built-in storage domain.
FAQ
- How is it different from session search?
- session_search only reads past conversation; dsh-memory stores durable facts the model writes itself — preferences, conventions and knowledge that survive across sessions.
- Where are records stored?
- In one storage domain (dsh_memory) routed through ctx.storageDomain, so persistence follows the deployment backend (json/sqlite) instead of hand-rolled files.
- Which tools does it register?
- memory_set, memory_get, memory_delete and memory_search — with tags, substring search and caps enforced at write time.
Alternatives
boomzikazita/dsh-memory · highland0971/dsh-native-memory · flymysql/dsh-memory