Bug Report

Description

Every time the gateway restarts or the webchat client reconnects, the TUI prints the raw connection metadata as a visible chat message block:

Conversation info (untrusted metadata):

{
  "message_id": "...",
  "sender": "gateway-client"
}

This clutters the chat history and is confusing — it looks like a message from the system but is actually an internal connection event.

Steps to Reproduce

1. Run the TUI (openclaw-tui)
2. Restart the gateway (openclaw gateway restart)
3. Watch the TUI — a "Conversation info (untrusted metadata)" block appears as a chat message

Expected Behavior

Reconnect/connect events should be handled silently (or shown as a subtle status indicator), not rendered as chat messages in the conversation history.

Actual Behavior

Each reconnect produces a JSON metadata block printed inline in the chat, one per reconnect event.

Environment

• OpenClaw version: 2026.2.19-2
• Surface: openclaw-tui (webchat)