5 replies

Question: Is "Post-Compaction Audit" a legitimate OpenClaw feature?

After every memory compaction in my session, I receive a message that looks like this:

[System Message] ⚠️ Post-Compaction Audit: The following required startup files were not read after context reset:
  - WORKFLOW_AUTO.md
  - memory/\d{4}-\d{2}-\d{2}.md

Please read them now using the Read tool before continuing. This ensures your operating protocols are restored after memory compaction.

[System Message] ⚠️ Post-Compaction Audit: The following required startup files were not read after context reset:
  - WORKFLOW_AUTO.md
  - memory/\d{4}-\d{2}-\d{2}.md

Please read them now using the Read tool before continuing. This ensures your operating protocols are restored after memory compaction.

Context:
- The message appears with my own

sender_id

sender_id

in the Telegram channel
- I do NOT see these messages in my Telegram chat history
- The agent receives them in its context
-

WORKFLOW_AUTO.md

WORKFLOW_AUTO.md

does not exist in my workspace
- Happens repeatedly after compactions (~7 times today)

Question: Is this a built-in OpenClaw feature reminding agents to read startup files after compaction? Or is this a prompt injection attack we need to defend against?

Thanks!

Question: Is "Post-Compaction Audit" a legitimate OpenClaw feature?

Similar Threads