Where each section moved
Every section heading from the previous single-page version keeps its anchor here, so an existing link such as/reference/session-management-compaction#when-auto-compaction-happens still resolves. Each entry points at the
page that now holds the content.
- Two persistence layers
- On-disk locations
- Store maintenance and disk controls
- Downgrading After The SQLite Flip
- Cron sessions and run logs
- Session keys (
sessionKey) - Session ids (
sessionId) - Session store schema
- Transcript event structure
- Context windows vs tracked tokens
- Compaction: what it is
- Chunk boundaries and tool pairing
- When auto-compaction happens
- Compaction settings
- Pluggable compaction providers
- User-visible surfaces
- Silent housekeeping (
NO_REPLY) - Pre-compaction memory flush
Troubleshooting checklist
- Session key wrong? Start with /concepts/session and confirm the
sessionKeyin/status. - Store vs transcript mismatch? Confirm the Gateway host and the store path from
openclaw status. - Compaction spam? Check the model’s context window (too small forces frequent compaction) and tool-result bloat (tune session pruning).
- Every prompt seems to overflow on a small local model? Confirm the provider reports the correct model context window. OpenClaw can cap the effective reserve only when that window is known.
- Silent turns leaking? Confirm the reply starts with the exact silent token
NO_REPLY(case-insensitive) and you are on a build that includes the streaming-suppression fix (2026.1.10+).