Commit Graph

4 Commits

Author SHA1 Message Date
James 9ff3c8cde9 fix: broadcast messages use agentchat session, not main
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.
2026-03-08 04:30:53 -04:00
James 27fb5ac215 feat: 1:1 routing fix + screenshot support
- Fix routing: direct messages now use 'agentchat-direct' session instead
  of 'main', preventing conflicts with active webchat sessions
- Add POST /api/upload endpoint for image uploads (10MB limit, png/jpg/gif/webp)
- Serve /uploads/ statically
- Pass images to agent via OpenAI multipart content (image_url type)
- UI: image preview bar above compose (attach button + Ctrl+V paste)
- UI: inline image display in chat bubbles with lightbox on click
- UI: '→ AgentName' badge on 1:1 messages
- Add github.com/google/uuid dependency for unique filenames
2026-03-08 04:30:00 -04:00
James bd003240a7 Add README with current architecture and status
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-08 04:18:13 -04:00
James a0cc49f4c9 agentchat: group chat for humans and AI agents
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>
2026-03-08 04:17:02 -04:00