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

docs: show current benchmark numbers on memory evaluation page (#6056)

Browse Source 
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Agam Pandey
2026-07-02 22:38:33 +05:30
committed by GitHub
co-authored by Claude Opus 4.8
parent 59484f066f
commit cd79fa8914
2 changed files with 37 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/core-concepts/how-it-works.mdx
+2 -1
View File
@@ -59,8 +59,9 @@ When you call `search`, Mem0 ranks stored memories against your query and filter
| **Semantic** | Vector similarity over embeddings | Conceptual questions |
| **Keyword** | Term matching for exact words and phrases | Names, IDs, and factual lookups |
| **Entity** | Boosts memories linked to entities in the query | Questions about a person, project, or account |
| **Temporal** | Scores candidates on time metadata extracted at write time against the query's temporal intent | Temporal questions ("when did...", current state, recency) |
Platform retrieval uses multiple signals in the managed service. OSS retrieval depends on your configured vector store, optional reranker, and graph store.
Platform retrieval fuses these signals in the managed service. OSS retrieval depends on your configured vector store, optional reranker, and graph store.
<Note>
Always scope searches with filters such as `user_id`, `agent_id`, or `run_id`. This keeps memories from different users, agents, or sessions from mixing.