JDSS/mem0
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: reinstate graph memory terminology (native entity linking) (#5601)

Browse Source
This commit is contained in:
rudrajmehta-mem0
2026-06-16 21:22:55 -07:00
committed by GitHub
parent d772f9a961
commit 6aa9bffa55
10 changed files with 126 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/platform/features/entity-scoped-memory.mdx
+4
View File
@@ -5,6 +5,10 @@ description: Scope conversations by user, agent, app, and session so memories la
Mem0's Platform API lets you separate memories for different users, agents, and apps. By tagging each write and query with the right identifiers, you can prevent data from mixing between them, maintain clear audit trails, and control data retention.
<Note>
**Entity IDs vs. graph entities.** This page covers the `user_id` / `agent_id` / `app_id` / `run_id` identifiers used to *scope* memories. These are different from the **graph entities** (the people, places, and concepts surfaced in [Graph Memory](/platform/features/graph-memory)).
</Note>
<Tip icon="layers">
Want the long-form tutorial? The <Link href="/cookbooks/essentials/entity-partitioning-playbook">Partition Memories by Entity</Link> cookbook walks through multi-agent storage, debugging, and cleanup step by step.
</Tip>