How do I know an agent really remembered a correction?
Validate a changed next action in a fresh session. Storage, retrieval and effective behavior are separate checkpoints.
- Published
- Oct 2, 2026
- Reviewed
- Oct 1, 2026
- Content updated
- Oct 2, 2026
- Applicable version
- Not pinned; check current documentation
- Underlying source date
- Not recorded
Before you start
- Check current account access, plan and task requirements.
“Saved” is not the acceptance criterion. A memory feature has value when corrected information changes a subsequent decision under the intended scope.
Use a falsifiable example
Use a synthetic preference such as “draft reports in English”. Correct it to Chinese, open a fresh conversation and ask for a report without repeating the language. Keep a second unrelated task to check that the correction does not leak across scopes.
Inspect each stage
Check the stored record, the retrieved evidence and the resulting action separately. A stale record being retrieved alongside the correction is a conflict to resolve, not extra context to celebrate.
Export, deletion and disconnect are separate product questions. A text file export does not prove complete task-state recovery.
Record the result
- Save old/new preferences, scope, session boundary and expected behavior.
- Record the actual next action and any manual reminder.
- Repeat after restart and test forgetting separately.
Evidence and limits
Official documentation checked
- Source-backed facts plus BotClaw editorial interpretation. No product account, inference or agent performance test was run.
Sources
Continue the decision
Cite or read with tools
https://botclaw.tech/items/obs-topic-memory