openclaw - 💡(How to fix) Fix [Feature] Add ootstrap.mode: persistent option to prevent BOOTSTRAP.md deletion [1 comments, 2 participants]

Problem

When a new session starts (/new), EasyClaw reads BOOTSTRAP.md and then deletes it as a "consume-once" mechanism. This is problematic for users who need the bootstrap content to persist across sessions.

Our use case: We have a startup self-check workflow (startup-check.py, memory-router.py recall, WAL sync, etc.) that needs to run on every session start. The current "read-then-delete" behavior means we have to either:

1. Recreate the file manually after each /new
2. Use workarounds like template files + auto-rebuild scripts

Proposed Solution

Add a configuration option in easyclaw.json:

json { "agents": { "defaults": { "bootstrap": { "mode": "persistent" } } } }

Or per-agent: json { "agents": { "list": [ { "id": "main", "bootstrap": { "mode": "persistent" } } ] } }

When mode: "persistent":

• BOOTSTRAP.md is read and injected into context on every /new
• The file is NOT deleted after reading
• The file remains available for subsequent sessions

Current Workaround

We already set "skipBootstrap": true and use AGENTS.md to reference our bootstrap logic, but this loses the clean separation that BOOTSTRAP.md provides.

Expected Behavior

Users should be able to choose between:

• consume (default): Current behavior - read once, delete (good for one-time setup prompts)
• persistent: Read on every session start, never delete (good for recurring workflows)

Environment

• EasyClaw Version: 1.3.52 (build 2026.5.18.548)
• OS: Windows 11 (26200)
• Channel: Telegram