- Add Room field to Message struct; carried through all routes
- Group room (default): existing broadcast behavior unchanged
- DM rooms (dm:James, dm:Mira, dm:Hans): messages route only to
that agent, replies stay in the DM room
- Agent↔agent DM: dm:Hans-James format; dmTarget() resolves peer
- UI: replace agent-bar with room-bar tab strip at top
- # group tab + one DM tab per agent (⚡ James, ✨ Mira, 🔧 Hans)
- Client-side room filtering: only show messages for active room
- Unread dot on inactive room tabs when new messages arrive
- Thinking indicator per room
- /api/send: accepts room field for agent-to-agent DMs
- Screenshots already supported (image_url); works in all rooms
All three agents (James/Mira on forge, Hans on Zurich) now use
session="main" for both direct and group messages. This lands
agentchat in each agent's primary thread — same context as
webchat/Telegram.
Previous v1.1 used "agentchat"/"agentchat-direct" sessions which
were isolated silos. Session "main" routes to agent:main:main on
whichever OC gateway is called, including Hans on Zurich.
When a human sends a group message (with or without name-mentions),
agents were being dispatched with direct=true, routing to the 'main'
session. This conflicts with active webchat/Telegram sessions on the
same agent, causing silent timeouts (context deadline exceeded).
Fix: broadcast/name-mention dispatches now use direct=false, which
routes to the 'agentchat' session. Only explicit To-field 1:1 messages
still use direct=true -> main session.
Identified from agentchat logs 2026-03-08. Issue: James messages
dropping when webchat session was active.
Go server with WebSocket UI, OpenClaw gateway integration,
persistent sessions, name-based routing, and cross-agent forwarding.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
James