sodamem/dsh-plugin-sodamem
Long-term DSH memory through a local SodaMem daemon: every turn recalls an evidence block and every closed turn is ingested, with no tool calls.
Makes memory unconditional instead of model-initiated. Recall happens while a turn is being assembled — the harness seam system-prompt/assemble retrieves an evidence block for that turn's question and contributes it to the prompt — and retain happens when the turn closes, via agent/turn-stopping, ingesting the turn's messages back into the store. Neither is a tool call, so the model cannot skip either one and neither costs tool-schema space; the README's comparison table makes the point that MCP cannot do this, because a tool is pull-only and nothing in the protocol lets a server contribute to the prompt or observe a turn closing. Retrieval fuses BM25, vector search and entities with no model call. Every recalled fact names the turn it came from, and facts carry four time axes — when the event happened, when the fact was true, when it was said and when it was stored — so a fact that stopped being true stops coming back. Retain ingests only what a human or the model actually said, excluding tool results and the runtime-context snapshot, because ingesting the snapshot would feed the store its own recalled output every turn. The one behaviour to know before relying on it: when recall misses its deadline the turn proceeds without memory, silently except for a ctx.logger.warn on every degraded turn.
Install
dsh plugin --profile tui add dsh-plugin-sodamemThe README's Install line, and it targets the tui profile as written — substitute your profile if you run web. The package ships a dsh.bundle manifest pointing at cordis.patch.yml, so dsh adds it to the profile's bundle list and composes a working default row; the README gives dsh --profile tui --dump-config | grep -A6 'id: sodamem' to confirm it landed. Two prerequisites are stated as prerequisites, not options: a running SodaMem daemon (sodamem daemon ensure, defaulting to http://127.0.0.1:8000) and Node >= 22. A patch-file route also exists for ad-hoc use without installing as a bundle (npx @deepseek-ai/dsh web --patch ./sodamem-plugin.patch.yml).
Compatibility
Needs Node >= 22 — the README notes the plugin uses AbortSignal.any — and a running SodaMem daemon; the plugin alone does nothing without it. This repository is only the DSH plugin: SodaMem is a separate open-source memory engine that runs as a local daemon, and the README warns not to run the MCP bridge and this plugin against the same store, because they would recall the same facts twice and ingest every turn twice. The daemon is pinned to a single worker by design, since per-user SQLite without cross-process WAL is not safe under concurrent writers, so two processes writing one SODAMEM_DATA_ROOT corrupt it. Concurrency is the documented limit: /v1/context latency grows near-linearly with concurrent clients, with medians of 128 / 211 / 361 / 672 ms at concurrency 1 / 2 / 3 / 4 on a real 1000-fact store. The README also retracts two earlier performance claims (a claimed 10/10 HTTP 500 cold start and a p50 of 17 ms) because they were measured against a store whose Chroma schema had been migrated.
Details
- Repo: sodamem/dsh-plugin-sodamem
- Category: Memory
- Stars: 2
- Version: 0.1.1 (npm)
Alternatives
jonasbu11/dsh-plugin-stet · dearbld/dsh-living-memory · fonlan/dsh-gitmemo