openclaw - ✅(Solved) Fix [Bug] WebChat Control UI displays internal exec notifications in user-visible chat [1 pull requests, 1 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#62418Fetched 2026-04-08 03:04:33
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×2cross-referenced ×1referenced ×1

WebChat Control UI shows internal system messages (exec completion notifications, session startup messages) directly in the user-visible chat transcript, which should not be exposed to end users.

Root Cause

WebChat Control UI shows internal system messages (exec completion notifications, session startup messages) directly in the user-visible chat transcript, which should not be exposed to end users.

Fix Action

Fixed

PR fix notes

PR #62421: fix(ui): hide internal exec notifications from WebChat chat transcript (#62418)

Description (problem / solution / changelog)

Summary

WebChat Control UI was displaying gateway-internal exec notifications (e.g. System: Exec completed, System (untrusted): Exec failed) in the user-visible chat transcript. These are implementation details that should not be shown to end users.

Root Cause

The buildChatItems() function in ui/src/ui/views/chat.ts renders all messages from the session history without filtering internal system events. Exec notifications are produced by session-system-events.ts with System: / System (untrusted): prefix and injected into the conversation for the AI context, but they should not appear in the user-facing WebChat UI.

Changes

  • ui/src/ui/chat/message-normalizer.ts: Add isInternalExecNotification() helper that detects system messages consisting entirely of exec notification lines (completed, failed, denied, timed out, finished)
  • ui/src/ui/views/chat.ts: Filter out internal exec notifications in buildChatItems() using the same skip pattern as tool result messages
  • ui/src/ui/chat/message-normalizer.test.ts: Add comprehensive tests for the new helper (trusted/untrusted, multi-line, non-exec system messages preserved, edge cases)

Test

pnpm test ui/src/ui/chat/message-normalizer.test.ts
# 35 passed (35)

Closes #62418

Changed files

  • ui/src/ui/chat/message-normalizer.test.ts (modified, +103/-0)
  • ui/src/ui/chat/message-normalizer.ts (modified, +25/-0)
  • ui/src/ui/views/chat.ts (modified, +12/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

WebChat Control UI shows internal system messages (exec completion notifications, session startup messages) directly in the user-visible chat transcript, which should not be exposed to end users.

Steps to reproduce

  1. Open WebChat Control UI in browser
  2. Run any exec command via the agent (e.g. openclaw plugins list, or any tool that triggers exec)
  3. Observe that exec completion/failure notifications appear in the user-visible chat transcript

Expected behavior

Internal exec notifications should not appear in the user-visible chat area. These are gateway implementation details that should be hidden from end users.

Actual behavior

The user sees internal system messages mixed with the conversation. Examples include:

  • "System: Exec completed (nova-rid, code 0) :: ..."
  • "System (untrusted): Exec failed (wild-sho, signal SIGKILL)"
  • Session startup messages injected via /new or /reset (e.g. "A new session was started via /new or /reset...")

These messages are confusing for non-technical users and clutter the conversation.

OpenClaw version

2026.4.5

Operating system

macOS Darwin 21.6.0 (x64)

Install method

No response

Model

minimax/MiniMax-M2.7

Provider / routing chain

openclaw -> minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Affected: WebChat Control UI users Severity: Annoying (confuses non-technical users, clutters conversation) Frequency: Every time an exec command runs Consequence: Users see cryptic internal messages mixed with their chat, degrading the user experience

Additional information

No response

extent analysis

TL;DR

Filtering or hiding internal system messages in the WebChat Control UI is likely necessary to resolve the issue.

Guidance

  • Review the WebChat Control UI code to identify where internal system messages are being rendered and consider adding a filter to exclude these messages from the user-visible chat transcript.
  • Investigate the possibility of modifying the exec command or its notifications to prevent them from being sent to the user-visible chat area.
  • Check the minimax model configuration and the openclaw provider setup to see if there are any options to suppress or redirect internal system messages.
  • Consider implementing a message classification system to distinguish between user-intended messages and internal system notifications, allowing for selective display.

Example

No specific code example can be provided without more details on the WebChat Control UI implementation, but a hypothetical filter might look like checking the message source or content before rendering it in the chat transcript.

Notes

The exact implementation details of the WebChat Control UI and the exec command system are not provided, which limits the specificity of the guidance. Additionally, the version of OpenClaw and the operating system might have implications for the available solutions, but without further information, it's difficult to tailor the advice.

Recommendation

Apply a workaround by filtering out internal system messages in the WebChat Control UI, as this approach does not require modifying the underlying exec command system or waiting for an update to OpenClaw. This can help mitigate the issue until a more permanent solution is implemented.

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 exec notifications should not appear in the user-visible chat area. These are gateway implementation details that should be hidden from end users.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING