docs: remove deprecated Graph Memory references (#5277)

2026-05-28 12:58:15 +05:30
parent add6aad40b
commit eaca45dcdb
21 changed files with 21 additions and 46 deletions
@@ -323,10 +323,6 @@ Metadata: {'verified': True, 'updated_date': '2025-04-02'}
 That “no duplicates” promise comes from the inference pipeline. Keep `infer=True` when you rely on automatic updates. Raw imports (`infer=False`) skip conflict checks, so mixing the two modes for the same fact will create duplicates.
 </Warning>

-**Maintains relationships:**
-
- If using graph memory, connections to other entities persist
-
 ### Pick the right inference mode

 | Mode | What it does | Best for | Watch out for |
@@ -216,7 +216,6 @@ This information was retrieved from your memory history where you previously men

 - **Smart Memory Management** - Organizes memories into searchable information *without setting up vector databases*
 - **Fast Retrieval** - Instant lookups with *sub-millisecond ping*, handles large datasets
- **Graph Capabilities** - Builds knowledge *automatically* as you push information
 - **Simple Integration** - Uses Mem0 API in the backend, works with *any MCP client* with just a few lines of code

 ### Gemini 3 + Mem0 Benefits
@@ -156,14 +156,7 @@ Here are some examples of how Mem0 can be integrated into various applications:
    icon="aws"
    href="/cookbooks/integrations/aws-bedrock"
  >
-    Mem0 with AWS Bedrock and Neptune.
-  </Card>
-  <Card
-    title="Graph Memory on Neptune"
-    icon="network-wired"
-    href="/cookbooks/integrations/neptune-analytics"
-  >
-    Graph memory with Neptune Analytics.
+    Mem0 with AWS Bedrock.
  </Card>
 </CardGroup>