Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
The Control UI displays async exec completion system events in the visible chat transcript instead of keeping them internal or clearly separated from normal chat messages.
Steps to reproduce
Open a direct session in the OpenClaw Control UI.
Trigger an async exec command that completes after the initial response.
Observe that completion events such as System (untrusted): Exec completed (...) and An async command you ran earlier has completed... appear in the visible chat transcript.
Expected behavior
Async exec completion events should remain internal to the agent/runtime or be shown only in a clearly separated system/debug area, not in the normal user-facing chat transcript.
Actual behavior
The visible chat transcript shows runtime/system messages including System (untrusted): Exec completed (...) and An async command you ran earlier has completed. The result is shown in the system messages above. Handle the result internally. Do not relay it to the user unless explicitly requested.
OpenClaw version
2026.4.15 (041266a)
Operating system
Linux 6.12.75+rpt-rpi-v8 (arm64)
Install method
pnpm
Model
openai-codex/gpt-5.4
Provider / routing chain
openclaw - oauth openai
Additional provider/model setup details
Auth profile shown in session status: openai-codex:default
Logs, screenshots, and evidence
Observed directly in the Control UI chat transcript.
Relevant runtime strings also appear in the installed OpenClaw build:
dist/session-system-events-*.js contains System (untrusted)
dist/heartbeat-runner-*.js contains An async command you ran earlier has completed... Handle the result internally...
Visible examples observed in chat:
System (untrusted): [timestamp] Exec completed (...)
An async command you ran earlier has completed. The result is shown in the system messages above. Handle the result internally. Do not relay it to the user unless explicitly requested.
Impact and severity
Affected users/systems/channels: Control UI users in visible chat sessions
Severity: Annoying and confusing; exposes internal runtime/system text in the normal conversation view
Frequency: Observed repeatedly during the session after async exec completions
Consequence: Internal system event text appears in the user-facing transcript and can be mistaken for normal assistant or user messages
Additional information
Observed on 2026-04-19 in a direct Control UI session while background exec commands completed asynchronously.. Before update from 01.April2026 it worked
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
The Control UI displays async exec completion system events in the visible chat transcript instead of keeping them internal or clearly separated from normal chat messages.
Steps to reproduce
Open a direct session in the OpenClaw Control UI.
Trigger an async exec command that completes after the initial response.
Observe that completion events such as System (untrusted): Exec completed (...) and An async command you ran earlier has completed... appear in the visible chat transcript.
Expected behavior
Async exec completion events should remain internal to the agent/runtime or be shown only in a clearly separated system/debug area, not in the normal user-facing chat transcript.
Actual behavior
The visible chat transcript shows runtime/system messages including System (untrusted): Exec completed (...) and An async command you ran earlier has completed. The result is shown in the system messages above. Handle the result internally. Do not relay it to the user unless explicitly requested.
OpenClaw version
2026.4.15 (041266a)
Operating system
Linux 6.12.75+rpt-rpi-v8 (arm64)
Install method
pnpm
Model
openai-codex/gpt-5.4
Provider / routing chain
openclaw - oauth openai
Additional provider/model setup details
Auth profile shown in session status: openai-codex:default
Logs, screenshots, and evidence
Impact and severity
Affected users/systems/channels: Control UI users in visible chat sessions
Severity: Annoying and confusing; exposes internal runtime/system text in the normal conversation view
Frequency: Observed repeatedly during the session after async exec completions
Consequence: Internal system event text appears in the user-facing transcript and can be mistaken for normal assistant or user messages
Additional information
Observed on 2026-04-19 in a direct Control UI session while background exec commands completed asynchronously.. Before update from 01.April2026 it worked