Feature Request
Problem
The webchat UI displays raw inbound metadata (conversation info JSON, timestamps, sender ID) as part of the user's message bubble. This technical envelope data is visible to the user, making the chat look cluttered and confusing.
Example
When a user sends "Brawo!", the webchat displays:
Conversation info (untrusted metadata):
{
"message_id": "a0ee5c1a-...",
"sender": "openclaw-control-ui"
}
[Thu 2026-02-19 10:33 EST] Brawo!
Instead of just:
Proposed Solution
- Strip/hide the metadata envelope from the displayed message in webchat
- Optionally show it in a collapsible "debug" section or developer mode
- The metadata is useful for the agent (context injection) but should not be visible to the end user
Why it matters
- Makes the webchat feel raw/unpolished
- Confusing for non-technical users
- The metadata is meant for the agent, not the human
Environment
Feature Request
Problem
The webchat UI displays raw inbound metadata (conversation info JSON, timestamps, sender ID) as part of the user's message bubble. This technical envelope data is visible to the user, making the chat look cluttered and confusing.
Example
When a user sends "Brawo!", the webchat displays:
Instead of just:
Proposed Solution
Why it matters
Environment