Dashboard FluxyChat Docs

How-to guides create-fluxy-chat CLI Multi-Platform Adapter Pattern Unified Chat API Troubleshooting integration Testing integrations Authentication (JWT)Migrate from Pusher / Ably / Sendbird Feature parity checklist Self-host one command Loop control StackBlitz examples fluxy.config.ts

MCP Client Integration Room as MCP server Role-scoped message visibility Hackathon cookbooks Presence-aware escalation Cross-org agent negotiation Agent room broadcast Critical action quorum External event ingest Multi-agent debate Interview eval template Presence knock template IoT telemetry starter Audience score template Audience score rollup Asymmetric session profiles Community decision simulation Live knowledge graph Room memory for operators HITL approval chain Fleet dispatch template Room OS positioning Built with patterns

Announcement channels Telephony to agent handoff

How-to Guides

Room OS positioning

Frame FluxyChat as infrastructure for humans + agents (PH-140).

Room OS for humans and agents

FluxyChat is not a chat widget SKU. It is a room operating system:

Humans and agents are peers on one timeline
Visibility scopes (room, whisper, role) control who sees what
External agents join via MCP with their own LLM keys
Cross-org negotiation, quorum acks, and presence escalation are primitives

Compare page and marketing copy should lead with these patterns, not feature parity tables alone.

See Hackathon cookbooks for proof from 35 weekend builds.

Fleet dispatch template

SAMU / SafeRide demo using FluxyFleet (PH-124).

Built with patterns

Anonymized hackathon pattern list (PH-142).

On this page

Room OS for humans and agents

Ask AI

FluxyChat documentation

Ask anything about FluxyChat — SDK, Worker API, agents, or deployment.

Answers are generated from docs context. Verify critical details in the guides.