DeepSeek Harness × Nowledge Mem
Install the community DeepSeek Harness bundle with Context Bundle, prompt-time recall, Mem MCP tools, and turn-end thread capture.
For your agent
Paste this into DeepSeek Harness or another agent helping with setup:
Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for DeepSeek Harness. Use the community DSH bundle, verify with nmem status and the Context Bundle or Working Memory check, then run one short DSH session and confirm nmem t list --source deepseek-harness shows the captured thread.DeepSeek Harness (dsh) is a plugin-first agent harness. Nowledge Mem uses the host's native Cordis lifecycle: startup context and recall are injected during agent/pre-step, Mem tools are bridged through DSH's MCP client, and real DSH transcript events are imported after turns finish.
This is a community plugin package published from nowledge-co/nowledge-mem-deepseek-harness. The repo is tagged dsh-plugin so DeepSeek Harness users can find it through the ecosystem convention.
Before You Start
- Nowledge Mem is running locally, or you have a reachable Nowledge Cloud / remote Mem endpoint
- DeepSeek Harness is installed and
dshworks nmemis onPATHin the same environment that launches DSH
nmem status
dsh --helpSetup
Install the community bundle into the DSH web profile:
dsh plugin --profile web add github:nowledge-co/nowledge-mem-deepseek-harnessRestart DeepSeek Harness:
dsh webIf you are installing from a local nowledge-co/community checkout instead of the published package:
dsh plugin --profile web add ./nowledge-mem-deepseek-harness-pluginRemote Mem
For Nowledge Cloud, Access Anywhere, self-hosted, or authenticated localhost, configure this machine once:
nmem config client set url https://your-server
nmem config client set api-key nmem_your_key
nmem config mcp show --host deepseek-harnessFor the DSH bundle itself, the most direct environment is:
export NMEM_MCP_URL="https://your-server/mcp"
export NMEM_API_KEY="nmem_your_key"Then restart dsh web.
Verify
Ask DSH:
Search my Nowledge memories for recent decisions about this project.Success means DSH can see the Mem MCP tools or the native recall message and returns results or a clean empty result.
Then run one short DSH session and check:
nmem t list --source deepseek-harnessYou should see a thread whose id begins with deepseek-harness-.
What The Bundle Uses
| DSH surface | Nowledge Mem behavior |
|---|---|
agent/pre-step | Injects the Context Bundle once per DSH session and adds prompt-time recall when the prompt looks like continuation, prior-decision, release, regression, connector, or plugin work. |
@deepseek-ai/dsh-mcp-client | Exposes Mem tools under the mcp__nowledge_mem__... namespace. |
session/event | Watches turn/end, serializes user/assistant/tool-result events, skips Mem's own injected context, and imports the conversation through nmem t import --source deepseek-harness. |
Known Limits
- DeepSeek Harness is in developer preview and may ship breaking plugin API changes.
- The connector captures new sessions while the bundle is active; historical DSH backfill is not claimed yet.
- DSH's MCP bridge currently exposes tools, not MCP resources or prompts.
- Thread capture depends on the local
nmemCLI being available to the DSH process.
Update
dsh plugin --profile web update nowledge-mem-deepseek-harnessRestart DSH after updating.
Related
- Connectors overview
- Customize connector behavior
- ZCode · MiMo Code · OpenCode
- Nowledge Mem DSH plugin: GitHub
- DeepSeek Harness: GitHub, CONTRIBUTING