OpenClaw Runtime: Memory Flush Write Paths Should Be Configurable

Problem

The memory flush mechanism (triggered when context window fills) currently restricts write tool calls to a single path: memory/YYYY-MM-DD.md. This is hardcoded in the binary at openclaw-tools-CUmYpN1l.js:775.

The system prompt (AGENTS.md in most workspaces) instructs agents to write two session-state files during flush:

1. memory/YYYY-MM-DD.md — daily log (works ✓)
2. memory/session-summaries/{channel}-{threadId}.md — structured session state (fails ✗)

Error:

Memory flush writes are restricted to memory/2026-04-29.md; use that path only.

Impact

• Agents cannot fully persist session state during flush (STEP 1 of the flush prompt fails).
• Session-summary writes get deferred to the next normal turn, causing a 1–2 turn delay in persistence.
• The flush prompt's documented workflow (3-step write) is not executable as written.
• This creates staleness: a future cold-start session reading today's daily log might miss session-summary context.

Reproduction

1. Set up a workspace with the standard flush prompt (ask for writes to both memory/YYYY-MM-DD.md and memory/session-summaries/{channel}-{threadId}.md).
2. Trigger a memory flush (fill context window).
3. Try to write to memory/session-summaries/telegram-1.md.
4. Observe error: "Memory flush writes are restricted to memory/2026-04-29.md; use that path only."

Proposed Solution

Add a configurable allowlist of paths for flush writes:

Config Schema

{
  "agents": {
    "defaults": {
      "compaction": {
        "memoryFlush": {
          "relativePath": "memory/YYYY-MM-DD.md",
          "allowedWritePaths": [
            "memory/YYYY-MM-DD.md",
            "memory/session-summaries/*.md"
          ]
        }
      }
    }
  }
}

Implementation

Modify wrapToolMemoryFlushAppendOnlyWrite in openclaw-tools-CUmYpN1l.js (line 761–789) to:

1. Accept allowedWritePaths: string[] in options.
2. Check if the requested path matches any pattern in the allowlist (using glob or regex).
3. Throw only if it matches none.

Default Behavior

If allowedWritePaths is not provided, default to [relativePath] (current behavior — backward compatible).

Workaround (Current)

Don't write session-summaries during flush. Write them on the next normal turn instead. This delays persistence by 1–2 turns but works.

Notes

• The flush prompt in AGENTS.md assumes both writes succeed. Either the prompt or the runtime needs to change.
• Suggestion: update the prompt to skip STEP 1's session-summary write during flush, or fix the runtime to allow it.