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

docs - replace session_id with run_id (#4742)

Browse Source
This commit is contained in:
szinvas
2026-04-10 20:06:59 +05:30
committed by GitHub
parent e59e3d5f0c
commit 789cc9d607
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/core-concepts/memory-operations/add.mdx
+1 -1
View File
@@ -21,7 +21,7 @@ Adding memory is how Mem0 captures useful details from a conversation so your ag
- **Messages** – The ordered list of user/assistant turns you send to `add`. - **Messages** – The ordered list of user/assistant turns you send to `add`.
- **Infer** – Controls whether Mem0 extracts structured memories (`infer=True`, default) or stores raw messages. - **Infer** – Controls whether Mem0 extracts structured memories (`infer=True`, default) or stores raw messages.
- **Metadata** – Optional filters (e.g., `{"category": "movie_recommendations"}`) that improve retrieval later. - **Metadata** – Optional filters (e.g., `{"category": "movie_recommendations"}`) that improve retrieval later.
- **User / Session identifiers** – `user_id`, `session_id`, or `run_id` that scope the memory for future searches. - **User / Session identifiers** – `user_id`, `agent_id`, or `run_id` that scope the memory for future searches.
## How does it work? ## How does it work?
docs/core-concepts/memory-types.mdx
+4 -4
View File
@@ -52,7 +52,7 @@ Mem0 maps these classic categories onto its layered storage so you can decide wh
Mem0 stores each layer separately and merges them when you query: Mem0 stores each layer separately and merges them when you query:
1. **Capture** – Messages enter the conversation layer while the turn is active. 1. **Capture** – Messages enter the conversation layer while the turn is active.
2. **Promote** – Relevant details persist to session or user memory based on your `user_id`, `session_id`, and metadata. 2. **Promote** – Relevant details persist to session or user memory based on your `user_id`, `run_id`, and metadata.
3. **Retrieve** – The search pipeline pulls from all layers, ranking user memories first, then session notes, then raw history. 3. **Retrieve** – The search pipeline pulls from all layers, ranking user memories first, then session notes, then raw history.
```python ```python
@@ -66,19 +66,19 @@ memory = Memory(api_key=os.environ["MEM0_API_KEY"])
memory.add( memory.add(
["I'm Alex and I prefer boutique hotels."], ["I'm Alex and I prefer boutique hotels."],
user_id="alex", user_id="alex",
session_id="trip-planning-2025", run_id="trip-planning-2025",
) )
# Later in the session, pull long-term + session context # Later in the session, pull long-term + session context
results = memory.search( results = memory.search(
"Any hotel preferences?", "Any hotel preferences?",
user_id="alex", user_id="alex",
session_id="trip-planning-2025", run_id="trip-planning-2025",
) )
``` ```
<Tip> <Tip>
Use `session_id` when you want short-term context to expire automatically; rely on `user_id` for lasting personalization. Use `run_id` when you want short-term context to expire automatically; rely on `user_id` for lasting personalization.
</Tip> </Tip>
## When should you use each layer? ## When should you use each layer?