{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "slow-stack-mneme--keep-memories-separate-per-agent-and-workspace",
 "repo": "slow-stack/mneme",
 "repo_url": "https://github.com/slow-stack/mneme",
 "repo_slug": "slow-stack-mneme",
 "title": "Keep memories separate across agents and workspaces",
 "page_title": "How to keep memories separate across agents and workspaces with Mneme",
 "summary": "Turn on scope isolation so memories from one project do not leak into another project's sessions.",
 "who": "A developer running several agents or projects that should not share context with each other.",
 "problem": "One memory pool mixes preferences and decisions from unrelated projects, so answers pick up the wrong context.",
 "outcome": "Each 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.",
 "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"
 ],
 "agent_prompt": "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.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "strictScope only hides memories that were explicitly declared to a scope, because automatic carrier tagging only lowers their weight in retrieval.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "javascript",
 "requirements": [
  "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"
 ],
 "risk": "sensitive",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/slow-stack-mneme/keep-memories-separate-per-agent-and-workspace/",
 "md": "https://dedupedai.com/use-cases/slow-stack-mneme/keep-memories-separate-per-agent-and-workspace/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/slow-stack-mneme--keep-memories-separate-per-agent-and-workspace.json",
 "api_version": "v1"
}