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.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…