refactor: drop history subcommand memory_history tool, update platform email mapping, adjust tests

This commit is contained in:
kartik-mem0
2026-04-05 01:32:47 +05:30
parent 6f43487c34
commit 5c14b4c594
4 changed files with 14 additions and 168 deletions
-3
View File
@@ -34,9 +34,6 @@ Identify which memories need action. Use the tools to investigate.
**Search for recent additions:**
Call `memory_search` with a `created_at` filter to find memories added since the last consolidation. These are the most likely to need merging or cleanup.
**Check edit history on suspicious entries:**
If a memory looks like it was updated multiple times or has contradictory content, call `memory_history` on it to understand how it evolved.
**Classify each target into one of these actions:**
- DELETE: contains credentials, expired by TTL, pure noise, raw tool output, standalone timestamps
- MERGE: two or more memories express the same fact in different words, or a series tracks incremental changes to the same entity