Encrypted 4-layer lifelong memory for DeepSeek Harness — powered by MindForge
Why dsh-mindforge?
DeepSeek Harness ships with basic session persistence — an append-only log and a simple memory table. That's enough for a single conversation, but agents forget everything across sessions, can't reason over past interactions, and have no way to encrypt sensitive memories.
dsh-mindforge plugs MindForge — a production-grade lifelong memory engine — directly into DSH as a native Cordis plugin. Your agent gets:
This is the same proven pattern used by dsh-mnemon — a TypeScript Cordis plugin wrapping an external CLI. The difference: MindForge brings encryption, 4-layer memory, federated ACL, and 6-way fusion search that no other DSH memory plugin offers.
Quick Start
Prerequisites
MindForge CLI — Install Python engine:
pip install MindForge
# Or from source:
git clone https://github.com/opok-ops/MindForge.git
cd MindForge
pip install -e .
MindForge init
# Or non-interactive (CI/CD):
MindForge init --no-encrypt
Node.js 22+ — Required by DSH.
Install Plugin
# From local path (development):
dsh plugin --profile web add "link:/absolute/path/to/dsh-mindforge"
# From GitHub (once published):
dsh plugin --profile web add "github:opok-ops/dsh-mindforge"
Configure
The cordis.patch.yml in this plugin provides defaults. Override in your DSH config:
mindforge:
cliPath: MindForge # or full path to executable
# dbPath: ~/.MindForge/data/store/memory.db
# keyFile: ~/.MindForge/data/store/key.bin
storageScope: global # global | workspace | custom
injectOnStep: true # auto-inject memories before each model step
maxContextTokens: 2048
tools: # choose which tools to expose to the model
- memory_add
- memory_search
- memory_context
- memory_stats
- memory_recall
- graph_query
All memory content is encrypted with AES-256-GCM at rest. The encryption key is stored separately from the database. Even if an attacker obtains the SQLite file, they cannot read the memories without the key file.
This makes dsh-mindforge suitable for enterprise and compliance-sensitive use cases that no other DSH memory plugin supports.
Federated Memory
Multiple agents can share memories through MindForge's federated layer:
dsh-mnemon is the other memory plugin in the DSH ecosystem. Both follow the same architecture (TypeScript plugin + external CLI). Key differences:
dsh-mindforge
dsh-mnemon
Engine
MindForge (Python)
mnemon (Go)
Memory layers
4
3
Encryption
AES-256-GCM
None
Search
6-way fusion
Semantic recall
Knowledge graph
Yes
Yes (4-graph)
Federated ACL
Yes
No
Memory evolution
Decay + cluster + link + reinforce + reflect
Capacity maintenance
CLI commands
201
~10
MCP tools
32
0
Tests
88 (Python) + vitest
vitest
Choose dsh-mindforge if you need encryption, federated memory, or the richest search. Choose dsh-mnemon if you prefer a single Go binary with no Python dependency.
