OpenClaw Memory System: Long-Term Context Storage

OpenClaw context has a boundary: the current session, the messages and tool results it can still see, and any memory or files that the configured workflow makes available. A persistent Gateway may keep state between conversations, but persistence does not mean that every old message is retrieved or that a provider sees a local-only copy.

Decide what should persist

• Keep the current task, constraints, and approval record in the active session.
• Store durable project facts in a reviewed file or memory workflow with a clear owner.
• Keep sensitive material out of long-lived context unless the retention and access path are explicit.
• Test retrieval with synthetic data before connecting a personal or shared channel.

Watch context growth

Pruning and compaction can reduce the context sent to a model, but they may remove the detail a reviewer needs to explain an action. Compare a short task and a longer handoff with the same provider, then record what remains visible after each policy change.

openclaw gateway status
openclaw doctor
openclaw security audit

Keep the data boundary legible

Document where the Gateway runs, which provider receives prompts, which files or skills can read memory, and how a backup is restored. The session concepts, session pruning reference, and security guide are the current sources for those decisions. Check the installed version before copying a command from this archive.