openclaw - 💡(How to fix) Fix bootstrap-injection truncation warning fires only once per session by default; silent across many sessions [1 comments, 2 participants]

Affected version

[email protected].

Summary

When a bootstrap-injected file (e.g. MEMORY.md) crosses the per-file char cap (default 12000), it gets silently truncated and the runtime emits one warning that is easy to miss. We had a real incident on 2026-05-04 where MEMORY.md grew to ~14K chars; recall was degraded across many fresh sessions before it was caught visually.

What we want

Default bootstrapPromptTruncationWarning: always so the warning surfaces every session that hits truncation, not just the first.

Or — better — surface it through openclaw doctor and the gateway-startup log line, not just the per-session warning channel. Truncation that quietly degrades agent recall floor across many sessions is exactly the kind of failure mode that should be loud at the operational layer, not buried in a per-session warning.

Workaround we're using

Set bootstrapPromptTruncationWarning: always in ~/.openclaw/openclaw.json and ship a per-machine daily-cron guardrail script that checks bootstrap-injected file sizes and warns before truncation hits.