Bug type

Regression (worked before, now fails)

Summary

Gateway correctly identifies control-ui connections but inbound metadata defaults channel to Slack.

Steps to reproduce

1. Open web dashboard (control-ui/webchat client)
2. Send a message to the agent
3. Check agent inbound metadata - sender_id will be correct but channel will be "slack"
4. Agent attempts to route response via message tool
5. Response goes to Slack instead of web dashboard

Expected behavior

Control-UI messages should have channel: "web" or channel: "control-ui" in inbound metadata, matching the actual client source. Response is routed back to the web dashboard.

Actual behavior

Inbound metadata contains channel: "slack" even though sender_id is "openclaw-control-ui" and gateway logs show client=openclaw-control-ui. Response is routed to Slack instead of web dashboard.

OpenClaw version

2026.3.2

Operating system

Linux 6.17.0-14-generic (Proxmox VM)

Install method

npm global

Logs, screenshots, and evidence

**Gateway logs show correct client identification:**

webchat connected conn=85a3746f-c877-4556-8cfc-f2852847113c remote=192.168.1.5 client=openclaw-control-ui webchat vdev


**Inbound metadata received by agent (WRONG):**

{
  "sender_id": "openclaw-control-ui",
  "sender": "openclaw-control-ui",
  "channel": "slack"  // ← BUG: should be "web" or "control-ui"
}


**Impact:** Agent message tool routes based on the `channel` field, not `sender_id`, so responses go to Slack instead of web dashboard.

Impact and severity

No response

Additional information

No response