# Check that a memory update changes the next session

A two-session test verifies persistence, correction and retrieval with a harmless fictional preference. A verbal promise to remember does not count as a saved memory.

- Citation: https://botclaw.tech/items/wf-memory-check
- Revision: 2
- Published: 2026-10-01T13:51:23.773Z
- Reviewed: 2026-10-01T00:00:00.000Z
- Updated: 2026-10-01T13:51:29.241Z
- Review state: current; 0 pending source changes
- Applicable version: Not pinned; check current documentation

Use a disposable profile or backed-up workspace. The test is deliberately small: one invented preference, one correction and one new session. Its goal is to distinguish a memory write from ordinary conversation context.

## Write, correct, reopen

1. Ask Hermes to save a fictional preference: for sample reports, use blue headings. Check the memory tool result or the actual saved record.
2. In a new session, request a sample report and check whether the preference influences its output.
3. Correct the preference to green headings and require the obsolete blue preference to be replaced or marked superseded.
4. Use /new and repeat the task. Verify both the stored correction and the next action. Remove only the disposable test record afterward.

## Evidence to keep

Capture the two memory writes, the new-session boundary and the observed report choices. A model remembering within one continuous chat does not prove persistence. A changed file with unchanged behavior does not prove the agent uses the update.


## Common failures

If the preference appears only before /new, inspect whether it was saved at all. If old and new preferences coexist, resolve the conflicting record and test a fresh session again. Do not reset a real user memory store to make the test pass.


## Evidence and limits

- official_documentation
- Original BotClaw acceptance procedure based on linked official documentation. Product commands were not executed; check your installed version.

## Sources

- https://hermes-agent.nousresearch.com/docs/user-guide/features/memory
