FluxyChat

Core SDK

AI collaboration

External workflows write Feeds and presence — not a second socket.

Three writers, one room:

RoleAPIWrites
CopilotuseAiChat / <AiChat />Local panel only
Room peerinvokeAgentChat messages
WorkflowPOST /rooms/:id/feeds + API keyFeed log + server_event

n8n / LangChain / a Worker cron uses the project API key (server-only):

curl -X POST "$WORKER/rooms/$ROOM/feeds/$FEED/messages" \
  -H "X-Fluxy-Api-Key: fc_…" \
  -H "Content-Type: application/json" \
  -d '{"body":"deploy ok","metadata":{"source":"n8n","status":"ok"}}'

Optional: the same process can mint a short-lived member JWT and send presence_patch { "agentStatus": "running" } on the room WebSocket so UIs show useOthers() status. Do not use client_event for that.

This is not MQTT, not a copilot transcript, and not HIPAA.