Who it is forA developer running several agents or projects that should not share context with each other.
The problemOne memory pool mixes preferences and decisions from unrelated projects, so answers pick up the wrong context.
The outcomeEach memory is tagged with the agent and workspace that wrote it, the current session's scope is preferred in retrieval, and strict mode hides explicitly scoped memories from other scopes.
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
- Open 设置 → 记忆库设置 in DSH
- Turn on scopeEnabled
- Save one memory in workspace A and one in workspace B from separate sessions (inferred, check the README)
- Turn on strictScope if explicitly scoped memories must be fully hidden from other scopes, then run a search from workspace B to confirm workspace A memories are down-weighted or hidden
Prompt for your agent
In the dsh-mneme repo, enable scopeEnabled, save a memory tagged to workspace A and another to workspace B, then search from workspace B. Expected output: workspace B memory ranked first and any workspace A memory down-weighted or hidden if strictScope is on. Verify the search result list for the scope tags.
Caveat. strictScope only hides memories that were explicitly declared to a scope, because automatic carrier tagging only lowers their weight in retrieval.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for slow-stack/mneme and "Keep memories separate across agents and workspaces"
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