openclaw - 💡(How to fix) Fix [Bug]: Control UI leaks internal async completion events into chat transcript [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#75232Fetched 2026-05-01 05:36:34
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
2
Author
Timeline (top)
closed ×1commented ×1labeled ×1

On OpenClaw 2026.4.24 (cbcfdf6), I’m seeing internal async exec completion events appear in the visible Control UI chat transcript even when user delivery is disabled.

This happens both:

when using the Control UI remotely over Tailscale and when using it locally on the OpenClaw machine In one case, the chat showed internal control text like:

async command completion notices reply HEARTBEAT_OK only instructions It also appeared with incorrect attribution in the chat surface, making the event look user-originated.

Root Cause

On OpenClaw 2026.4.24 (cbcfdf6), I’m seeing internal async exec completion events appear in the visible Control UI chat transcript even when user delivery is disabled.

This happens both:

when using the Control UI remotely over Tailscale and when using it locally on the OpenClaw machine In one case, the chat showed internal control text like:

async command completion notices reply HEARTBEAT_OK only instructions It also appeared with incorrect attribution in the chat surface, making the event look user-originated.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

On OpenClaw 2026.4.24 (cbcfdf6), I’m seeing internal async exec completion events appear in the visible Control UI chat transcript even when user delivery is disabled.

This happens both:

when using the Control UI remotely over Tailscale and when using it locally on the OpenClaw machine In one case, the chat showed internal control text like:

async command completion notices reply HEARTBEAT_OK only instructions It also appeared with incorrect attribution in the chat surface, making the event look user-originated.

Steps to reproduce

  1. start openclaw
  2. just wait - heartbeat requests and replies appear in chat
  3. the following will print to chat at times:

System (untrusted): [2026-04-30 15:10:49 EDT] Exec completed (brisk-bl, code 0) :: nsteoOS1PbQmevO8g9iL8"}"}],"api":"openai-responses","provider":"local","model":"qwen35-codeforces-27b-rl-step25-Q4_K_M.gguf","usage":{"input":24139,"output":266,"cacheRead":0,"ca…

An async command completion event was triggered, but user delivery is disabled for this run. Handle the result internally and reply HEARTBEAT_OK only. Do not mention, summarize, or reuse command output. Current time: Thursday, April 30th, 2026 - 3:11 PM (America/New_York) / 2026-04-30 19:11 UTC

An async command completion event was triggered, but user delivery is disabled for this run. Handle the result internally and reply HEARTBEAT_OK only. Do not mention, summarize, or reuse command output. Current time: Thursday, April 30th, 2026 - 3:11 PM (America/New_York) / 2026-04-30 19:11 UTC

Expected behavior

internal async completion events should stay hidden when user delivery is disabled internal control/heartbeat instructions should never appear in chat sender attribution should remain correct

Actual behavior

internal event text is exposed in the Control UI transcript attribution/routing appears incorrect

OpenClaw version

2026.4.24 (cbcfdf6)

Operating system

Ubuntu 24.xx

Install method

npm global

Model

openai.gpt5.4 / deepseek v4 pro

Provider / routing chain

openclaw --> openai oauth or ollama api

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

Disable user delivery for internal async completion events in the OpenClaw configuration to prevent them from appearing in the Control UI chat transcript.

Guidance

  • Review the OpenClaw configuration to ensure that user delivery is properly disabled for internal async completion events.
  • Check the routing chain and attribution logic to prevent internal control instructions from being exposed in the chat transcript.
  • Verify that the OpenClaw version (2026.4.24) is correctly handling internal events when user delivery is disabled.
  • Investigate the possibility of a bug in the OpenClaw code that is causing internal events to be incorrectly attributed to users.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be related to a bug in the OpenClaw code or a misconfiguration of the user delivery settings. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by disabling user delivery for internal async completion events in the OpenClaw configuration until a fix is available. This should prevent internal events from appearing in the Control UI chat transcript.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

internal async completion events should stay hidden when user delivery is disabled internal control/heartbeat instructions should never appear in chat sender attribution should remain correct

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Control UI leaks internal async completion events into chat transcript [1 comments, 2 participants]