Skip to content

Conversation

@azarboon
Copy link
Contributor

@azarboon azarboon commented Jan 27, 2026

Description

What changed:
This change clarifies that the memory used in the memory agent workflow is short-term, using the same terminology as the mem0 documentation, and is scoped to the current session by default. It also directs users to the relevant configuration and documentation for enabling persistence across sessions. Links to the appropriate mem0 documentation are added to improve discoverability and navigation.

Why this change is needed:
The current documentation is largely silent and somewhat misleading regarding memory persistence. This ambiguity is compounded by the fact that mem0’s own documentation is vague on this topic. I had to spend time verifying the actual behavior, and this change aims to save that effort for future readers. The updated text aligns expectations with the default behavior and provides clear pointers to configuration options for enabling persistence.

Related Issues

Type of Change

  • New content
  • Content update/revision

Checklist

  • I have read the CONTRIBUTING document
  • My changes follow the project's documentation style
  • I have tested the documentation locally using mkdocs serve
  • Links in the documentation are valid and working

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@azarboon azarboon changed the title Clarify short-term nature of memory in documentation docs: clarify short-term nature of memory in documentation Jan 27, 2026
@azarboon azarboon changed the title docs: clarify short-term nature of memory in documentation docs: clarify short-term memory behavior in the memory example Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant