openclaw - 💡(How to fix) Fix [Bug]: Internal provenance / async completion text still leaks into chat on 2026.5.7

Summary

OpenClaw 2026.5.7 still leaks internal orchestration/provenance text into visible chat across multiple surfaces:

• Control UI / webchat
• TUI
• WhatsApp direct chat

The leaked text includes inter-session provenance wrappers and internal runtime context, not just the older inbound-metadata envelope case.

This appears related to the broader family behind #72918 and the attempted fix stream around #68262, but the published 2026.5.7 tarball does not appear to contain the key suppression behavior that should keep these messages out of user-visible history.

What I observed

Examples of leaked content seen in chat history / visible output:

• Conversation info (untrusted metadata):
• Sender (untrusted metadata):
• [Inter-session message] sourceSession=... sourceChannel=... sourceTool=... isUser=false
• <<<BEGIN_OPENCLAW_INTERNAL_CONTEXT>>>
• OpenClaw runtime context (internal):
• internal async completion / heartbeat text such as:
  • An async command completion event was triggered, but user delivery is disabled for this run.
  • Handle the result internally and reply HEARTBEAT_OK only.

The same class of leak was reproduced/observed in:

• WhatsApp direct chat
• TUI history display
• Control UI / webchat

Why I think this is a real release gap, not local drift

I checked the installed package and the published npm tarball for [email protected] and they match byte-for-byte for the relevant built files.

So this is not a local install corruption issue.

I also inspected the built dist files and could not find the newer internal_system history suppression path that appears in #68262-related diffs.

Likely relationship to prior issues / PRs

This seems closest to the fix stream around:

• #72918 — Control UI leaks internal async completion / heartbeat system messages into chat
• #68262 — source-tag internal prompts to hide them from chat history

But the actual leak here is broader:

• inter-session provenance wrappers ([Inter-session message] ... isUser=false)
• subagent announce / completion delivery
• internal runtime context blocks
• visible async completion / heartbeat text

Expected behavior

Internal orchestration text should be consumed silently and must not be rendered in:

• Control UI / webchat chat bubbles
• TUI visible history
• delivery to external channels like WhatsApp

Actual behavior

The internal/provenance text is persisted and then re-surfaced in user-visible output on multiple surfaces.

Environment

• OpenClaw: 2026.5.7
• Install: published npm tarball
• Node: v25.9.0
• Surfaces: Control UI, TUI, WhatsApp direct chat

Notes

I also checked the task-cancel shim separately; that was stale and has been refreshed, but it looks unrelated to this leak.

Requested fix area

Please verify the shipped build includes the intended chat-history suppression for provenance-tagged/internal-system messages, especially around:

• inter-session provenance annotation / persistence
• subagent announce delivery
• history projection / sanitization for user-visible transcript rendering
• Control UI / TUI / channel delivery paths