{
  "id": 7249037,
  "title": "Why do Cursor and Claude Code both say connected to my memory server and still share nothing?",
  "url": "https://urgent.news/2026/09/14/why-do-cursor-and-claude-code-both-say-connected-to-my-memory-server",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-14T05:19:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/izgorodin/why-do-cursor-and-claude-code-both-say-connected-to-my-memory-server-and-still-share-nothing-43jo"
  },
  "original_language": "en",
  "account": "Cursor and Claude Code both indicate they are \"connected to my memory server\" yet still share no information. This occurs because the connection is merely a technical link, while actual sharing depends on the account setup. All clients pointing to the same backend are considered connected, but without the same account, no information is exchanged.\n\nFor Mnemoverse, the setup step is a single API key. Every client connected to this key shares memory by default. Changing the key creates a separate account, ending sharing. The browser sign-in in VS Code bypasses this key and automatically connects to the same account system.\n\nCognee offers two modes: Standalone, where each instance has its own database, and API, where instances connect to a shared backend. The former prevents sharing, while the latter allows it. However, Cognee's API Mode shares a single token for all writes, effectively creating one Cognee user account.\n\nMem0 requires a unique identifier for each user. Two tools using the default identifier will not share memory, as they end up in separate namespaces. Setting a custom identifier enables shared memory across tools.\n\nSupermemory, designed for shared memory, requires each client to select which spaces (identifiers) it can access. If two clients are authorized to different spaces, or have different active spaces, they will not share memory. Supermemory relies on this setup choice to determine sharing.",
  "summary": "You write a decision down in Cursor at four in the afternoon: the payments service keeps its own retry table, do not fold it into the queue. At six you open Claude Code on the same repository. The memory server is connected in both editors, and the agent proposes folding the retry table into the queue. You read the memory back from Cursor and the note is there. You read it back from Claude Code…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 2,
    "also_reported_by": [
      {
        "outlet": "Dev.to",
        "title": "I replaced most of a dev team with Claude Code to build a production e-commerce store. Here's what broke.",
        "url": "https://urgent.news/2026/09/14/i-replaced-most-of-a-dev-team-with-claude-code-to-build-a-production",
        "published": "2026-09-14T05:23:10.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}