dsh-auto-memory

dsh-auto-memory

English | 中文 ### Your dsh agent forgets everything you tell it. Every. Single. Session. Fix it with one command. Claude Code-style persistent memory for DeepSeek Harness — native, zero servers, zero embeddings, zero setup.

Say *"Remember: I'm a Python backend engineer preparing for interviews"* today — open a brand-new session tomorrow, ask *"what do you know about me?"*, and it remembers. Highlights

1.6 — memory has a shelf life: time-sensitive facts (plans, prices, versions) carry a validUntil; expired memories stop being injected, surface on the health board with one-click renew, and are marked as historical when recalled. High-recall memories now rank higher in the index (a gentle reads multiplier), and writes carrying secrets get an explicit "redacted" receipt instead of silent sanitization.

1.5 — a panel, not a wall: tabbed UI (Memories first-class, Insights, Health, Settings), monochrome SVG iconography, color-blind-checked identity colors — and health rows jump straight to the memory card they're about.

1.4 — runtime settings + a recall funnel: a Settings card (presets, sliders, per-field reset) changes the injection budget, value gate and eviction at runtime — next request, no restart; the recall funnel makes "injected but never actually read" visible and actionable (mute the budget hogs, pin the buried gems).

1.x — trustworthy memory + measured end-to-end: consolidation products are born candidate with verbatim evidence quotes; only *you* can grant verified; disputed memories are never re-injected; every write passes an injection-pattern guard at the store choke point. And it's measured: four evaluation layers (deterministic / recall / consolidation / end-to-end) plus a LongMemEval-S alignment run — including an honestly published off-target score. Full history: CHANGELOG.md · Releases Claude Code has this. dsh didn't. Now it does.

DeepSeek Harness is the hottest open agent harness on GitHub right now — models, tools, sandboxes, everything is a plugin. But it ships with no memory subsystem at all. The official answer is three *default-off* MCP configs to third-party servers, which the official docs themselves qualify: not auto-injected, no forgetting policy, substring-only search. Your agent has amnesia by design.

dsh-auto-memory closes that gap natively: Memories are ordinary files under $DSH_HOME/memory/ — hand-editable, grep-able, git-friendly, yours. Trustworthy, not just persistent (1.0.0)

Model-consolidated memories can be confidently wrong — and a wrong memory gets re-injected every session. So memories carry a trust status: consolidation products are born candidate (with a verbatim evidence quote from the transcript — fabricated citations are dropped by checking against it), verified can only be granted by *you* in the panel, disputed / superseded are never injected. Every write path passes an injection-pattern guard at the store choke point; content changes downgrade trust and expire old evidence. A 🩺 health board surfaces unverified / zombie / conflicting memories for review. Same flat files, same zero services — now with an audit trail for *whether to believe them*. One minute to feel it

Or for real, in a chat: tell your agent things worth remembering. The model calls memory_write / memory_read / memory_list / memory_search / memory_delete, following Claude Code's write discipline: dedupe-and-update over piling up, absolute dates only, [[name]] cross-links, feedback memories carry Why: / How to apply: lines. The memory panel