Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading to openclaw 2026.3.31, the internal Pre-compaction memory flush prompt is no longer silent. It is rendered directly in the chat window, even though this mechanism is supposed to be an internal housekeeping step.
More importantly, the memory flush can preempt the active user turn. When I send a normal message in a long-running session, OpenClaw sometimes runs the memory flush first, and only then continues with my actual question. This interrupts the conversation flow and makes the UI feel stuck or hijacked by an internal system task.
I did not observe this behavior in 2026.3.28.
Steps to reproduce
Upgrade to openclaw 2026.3.31
Open or continue a long session with enough context/history
Send normal user messages
When the session gets near compaction thresholds, the UI shows Pre-compaction memory flush...
The flush may run before the actual user request is answered
Expected behavior
Pre-compaction memory flush should remain completely invisible to the user.
Internal memory flush runs should not appear as visible chat content.
A user’s active message should be handled first.
Memory flush should not block or preempt the foreground conversation turn.
Actual behavior
A long internal prompt beginning with Pre-compaction memory flush. appears in the chat UI.
During normal conversation, OpenClaw may pause my actual request and run the memory flush first.
My question is delayed while the system performs memory housekeeping.
OpenClaw version
2026.3.31
Operating system
mac os 15.6.1
Install method
npm
Model
kimi-2.5
Provider / routing chain
Control UI -> agent -> memory-core flush
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
disrupts conversation continuity
confuses users by exposing internal prompts
makes long sessions noticeably worse to use
Additional information
No response
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
After upgrading to openclaw 2026.3.31, the internal Pre-compaction memory flush prompt is no longer silent. It is rendered directly in the chat window, even though this mechanism is supposed to be an internal housekeeping step.
More importantly, the memory flush can preempt the active user turn. When I send a normal message in a long-running session, OpenClaw sometimes runs the memory flush first, and only then continues with my actual question. This interrupts the conversation flow and makes the UI feel stuck or hijacked by an internal system task.
I did not observe this behavior in 2026.3.28.
Steps to reproduce
Upgrade to openclaw 2026.3.31
Open or continue a long session with enough context/history
Send normal user messages
When the session gets near compaction thresholds, the UI shows Pre-compaction memory flush...
The flush may run before the actual user request is answered
Expected behavior
Pre-compaction memory flush should remain completely invisible to the user.
Internal memory flush runs should not appear as visible chat content.
A user’s active message should be handled first.
Memory flush should not block or preempt the foreground conversation turn.
Actual behavior
A long internal prompt beginning with Pre-compaction memory flush. appears in the chat UI.
During normal conversation, OpenClaw may pause my actual request and run the memory flush first.
My question is delayed while the system performs memory housekeeping.
OpenClaw version
2026.3.31
Operating system
mac os 15.6.1
Install method
npm
Model
kimi-2.5
Provider / routing chain
Control UI -> agent -> memory-core flush
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
disrupts conversation continuity
confuses users by exposing internal prompts
makes long sessions noticeably worse to use
Additional information
No response