Bug type

Regression (worked before, now fails)

Summary

In webchat/control UI, the silent reply token NO_REPLY is rendered as a visible assistant message bubble (shown as just "NO" in the UI, likely underscore truncation). This happens during silent housekeeping turns such as the pre-compaction memory flush. NO_REPLY should suppress user-visible output.

Steps to reproduce

1. Open the Control UI (webchat) connected to a local gateway.
2. Use the chat long enough to trigger the pre-compaction memory flush housekeeping turn.
3. Observe a visible assistant message bubble containing “NO” / “NO_REPLY”.

Expected behavior

NO_REPLY should be treated as a silent token and never rendered in webchat output.

Actual behavior

A visible assistant message bubble appears containing "NO" (and/or NO_REPLY). The session transcript contains assistant turns whose full text is exactly NO_REPLY.

OpenClaw version

2026.3.1

Operating system

Linux Mint 22.3

Install method

No response

Logs, screenshots, and evidence

Impact and severity

Affected: webchat users
Severity: Medium-high (breaks silent housekeeping UX; confusing output)
Frequency: repeatable whenever memory flush triggers
Consequence: internal/silent sentinel text leaks into the visible chat UI

Additional information

Related: locked thread about this symptom; similar public report exists (#3340). Likely a gap between channel-delivery silent filtering and webchat transcript rendering.