mem0 memory reading and token limit handling
Cluster 37421 · agent. Data as of
Nothing open on GitHub. Fix merged in #106542 on 9 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #106542. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items relate to reading agent-attributed memories in mem0 and handling INPUT_TOKEN_LIMIT_EXCEEDED errors, including a silent data-loss issue when long conversations exceed token limits and a fix to retry with truncated content.
Open issues0
Open PRs0
Fixes on record
-
#106542 mem0 memory no longer drops long turns; sync cap configurable per embedder (#37421, #106235, salvage #37427)
files:
plugins/memory/mem0/README.md,plugins/memory/mem0/__init__.py,tests/plugins/memory/test_mem0_v3.py,website/docs/user-guide/features/memory-providers.md
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#37421mem0 sync_turn silently drops long conversations on INPUT_TOKEN_LIMIT_EXCEEDED
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #106542
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 9 Sep 2026