ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-12 21:53:00 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(memory): explain overlapping hook and transcript indexing (#118299)

Browse Source
This commit is contained in:
Peter Steinberger
2026-08-02 17:06:32 -07:00
committed by GitHub
parent c6ef95604e
commit cef675233b
2 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/reference/memory-config.md
+12
View File
@@ -465,6 +465,18 @@ Index session transcripts and surface them via `memory_search`:
Session indexing is opt-in and runs asynchronously. Results can be slightly stale. Session logs live on disk, so treat filesystem access as the trust boundary.
</Warning>
<Note>
The [session-memory hook](/automation/hooks#session-memory) saves conversation
excerpts to `<workspace>/memory/`, which the `memory` source already indexes.
If transcript indexing is also enabled, the same conversation can appear from
both `memory` and `sessions`, resulting in overlapping search results and
additional embedding work. For hook-only recall, set `sources: ["memory"]` and
`rememberAcrossConversations: false`; `sources` alone is insufficient because
cross-conversation recall automatically adds `sessions`. For full-transcript
recall instead, run `openclaw hooks disable session-memory`. Enable both only
when you intentionally want both representations.
</Note>
Ordinary model-invoked session transcript search obeys
[`tools.sessions.visibility`](/gateway/config-tools#toolssessions). The default
`tree` visibility exposes the current session, sessions it spawned, and