Credentials. The daemon uses the same token as the DSH panel and CLI, so anyone who obtains it can read and change the memory library.
Who it is forA developer building a script, web bridge, or custom panel that needs memory access while DSH is not open.
The problemMemory is only reachable while DSH runs, which blocks integrations that work at other times.
The outcomeA resident daemon on 127.0.0.1:8790 serves the memory library, and your script reads and writes it with the same token used by the DSH panel and CLI.
What you need first
- DeepSeek Harness (DSH) installed, with the dsh command available
- Node.js and npm for the MCP server and the standalone daemon
- Access to the DSH settings panel to generate an external access token
Steps
- Install the package globally:
npm i -g @modusensus/dsh-mneme - Start the daemon:
dsh-mneme-serve - Copy the token used by the DSH panel and CLI into your script's configuration
- Send an authenticated HTTP request from your script to 127.0.0.1:8790 to list recent memories and confirm a response (inferred, check the README)
Prompt for your agent
In the dsh-mneme repo, start the daemon with dsh-mneme-serve and send one authenticated request to 127.0.0.1:8790 using the token in <token-file>. Expected output: a successful response listing memories. Verify that the daemon refuses to start if port 8790 is already in use.
Caveat. The first phase of the daemon has no LLM, so consolidation and distillation still depend on the DSH host, and the port cannot be shared with DSH external access.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for slow-stack/mneme and "Read and write memory from scripts with DSH closed"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer