Quick answer: Do not add another conflicting copy of the same fact. Identify the single valid memory, review any pending Memory Change Request, and remove or correct conflicting entries one at a time. Then test recall in the intended chat scope.
Identify duplicate, outdated, and conflicting entries
Duplicates repeat the same fact. Conflicts contain different statements about the same fact. An outdated memory can be accurate historically but wrong now. A Memory Change Request may propose replacing or updating an existing entry instead of adding a new one, so review pending requests before manual cleanup. Keep a note of the intended current fact before editing the panel.
If no memory is being created, use the saving workflow. If the correct memory exists but is ignored, use the recall guide.
AI Video Gallery
A preview of selected portrait videos and AI character images.
Clean the panel without creating a new loop
- Choose the entry that should remain.
- Review pending change requests before making manual edits.
- Correct or remove one conflicting entry.
- Wait for the panel to update.
- Test recall in one chat using the intended scope.
- Only then remove the next duplicate if necessary.
Avoid mass deletion. It can erase context that helps explain how the conflict occurred.
After each change, test one direct question in the intended chat. A correct panel does not prove the companion will recall the fact in every context; the goal is to remove contradictory inputs first, then evaluate recall separately.
Check whether the scope is creating legitimate differences
Private chats and separate Memory Groups can correctly hold different versions for different scenarios. Do not merge them merely because the companion is the same. Use the Memory Group guide when the wrong chats appear to share information.
Visit the SecretOpedia’s Secrets AI memory-cleanup guides for the complete memory cluster. The the Secrets AI review of memory management provides broader product context.
Escalate recurring duplicates with a minimal timeline
Contact support when a corrected entry repeatedly duplicates itself or an approved change does not apply. Include the companion, scope, relevant entry text, time, and action taken.
The changelog has previously listed duplicate-entry edge cases and smarter memory merging. Treat this as historical product context rather than a current-status claim.
Sources checked July 12, 2026: Memory System, Multiple Chats, Changelog, Tips & Tricks.
