dsh-memento: Approval-Gated Cross-Session Memory for DeepSeek Harness
perrylink/dsh-memento
Bounded, layered, approval-gated and auditable cross-session memory for DeepSeek Harness, backed by a typed ctx.memory seam and a local SQLite store.
dsh-memento is a DSH plugin that gives DeepSeek Harness long-term memory, turning "remember the last session" into a bounded, layered, approval-gated and auditable capability seam. It targets the pain of models writing memory with no gatekeeper and no way to trace it afterwards: every write path passes through the approval waterfall inside the service, which no model path can bypass. Memory is kept in a local SQLite store, recall is layered and size-limited, a frozen snapshot gives each session a stable starting view, and an audit table lets you reconstruct write history.
How to Install
dsh plugin --profile web add dsh-memento- Category
- Memory & Context
- Platform
- DSH Plugin
- Author
- perrylink
- Distribution
- Plugin
dsh-memento Key Features
dsh-memento Repo Summary
What Does It Do?
Memento is a DSH plugin for DeepSeek Harness that turns cross-session memory into a bounded, layered, approval-gated and auditable capability seam. It solves the problem of models writing memory with no gatekeeper and no way to trace what happened later: every write path is forced through an approval waterfall that no model path can bypass. Maintained by PerryLink under Apache-2.0, it runs on Windows, macOS and Linux as a pure host plugin with no native code and no network access.
Core Features
- Unbypassable approval gate: every write path (
add/replace/remove/seed) goes through the approval waterfall inside the service rather than the tool layer, andwritePolicy(ask / auto / off) is model-invisible configuration. - Local SQLite provider: memory lives in a database under the DSH home directory using WAL mode and 0600 permissions, so data stays on the machine.
- Bounded, layered recall: results are organised in layers and size-limited instead of dumping whole histories back into context.
- Rebuildable audit trail: the approval pair plus the plugin's own audit table let you reconstruct write history, with the session-log gap named out loud.
- Frozen snapshot injection: a frozen snapshot is injected into the system prompt so the model starts each session with a stable memory view.
- Typed
ctx.memoryservice: memory is exposed as a capability seam that thememorytool and other consumers can call.
How to Use This Plugin?
After enabling it in DSH, the plugin registers the memory tool and injects a frozen snapshot into the system prompt, so you simply ask it to remember or change something during a session. Writes trigger the approval flow and only land after you confirm; to adjust behaviour, edit the editable fields such as writePolicy in the config form, and accepted edits are committed into the running plugin instead of remounting it. The plugin is frozen as of 2026-10-05 with no new features, though existing installs keep working and only genuine breakage will be fixed.
How to Troubleshoot This Plugin?
If the plugin is skipped by the compatibility guard on a newer host, it is usually because its declared dsh peer range caps below the host version, so add an exemption as described in the official notes. If the config form does not take effect, note that newer versions replaced the old settings registration surface with live Config forms, where a form's namespace is the profile entry id and its editable fields are the .volatile() ones.
This page is an independent rewrite of the plugin's official README — for authoritative documentation and the latest changes, refer to the source: perrylink/dsh-memento. The plugin is third-party code that runs on your machine once installed; inclusion does not imply endorsement — please review the source before installing.