openclaw - 💡(How to fix) Fix Bug: WebChat inter-session messages displayed with user's name instead of system label [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#81263Fetched 2026-05-14 03:33:55
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
Timeline (top)
closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

Describe the bug

In the OpenClaw webchat (Control UI), inter-session messages (specifically `subagent_announce> messages from child sessions) are rendered in the chat flow without a clear sender identifier, making them appear as if the user sent them.

Steps to Reproduce

  1. Spawn a sub-agent via `sessions_spawn` from a webchat session
  2. Wait for the sub-agent to complete
  3. The completion announcement (`subagent_announce>) is routed back to the parent webchat session
  4. In the Control UI, the announcement message appears inline with the conversation, styled/attributed as if it came from the user rather than as a system notification or assistant message

What happened

The inter-session message includes:

  • `[Inter-session message] sourceSession=... sourceTool=subagent_announce isUser=false>
  • Relevant memories context block
  • The sub-agent result

This entire block was rendered in the chat window in a way that made the user think their own name was associated with the message.

What you expected to happen

Inter-session messages (especially `isUser=false> announcements) should be:

  • Visually distinct from user messages (e.g., different background, icon, or label like "System" / "Task Result")
  • Not attributed to the authenticated user
  • Or at minimum, clearly marked as internal/system messages

Environment

  • OpenClaw version: 2026.5.7
  • Channel: webchat (Control UI)
  • OS: macOS 26.4.1 (arm64)
  • Node: 25.9.0

Additional context

The inter-session message envelope shows `isUser=false> and `sourceChannel=webchat>, so the metadata correctly identifies this as a non-user message. The bug is in the UI rendering layer — it does not distinguish between:

  • Direct user messages
  • Inter-session system messages routed to the webchat session
  • Assistant replies

This causes user confusion as they see technical internal routing details and sub-agent results appearing under their own name in the chat.

Screenshots

User reported: message appeared with technical content (relevant memories, sub-agent results) in the chat window, attributed to the user's identity.

Related issues

  • #66934 - WebChat sender label shows 'openclaw-control-ui' instead of 'you'
  • #44153 - sessions_send from sub-agent flips parent session deliveryContext
  • #51851 - WebChat UI hangs after /new — inter-session message not displayed

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…

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: WebChat inter-session messages displayed with user's name instead of system label [1 comments, 2 participants]