How-to Guides

Feature parity checklist

What the JS SDK and Worker cover vs typical hosted chat APIs.

Use this when you are mapping from Pusher, Ably, or a custom WebSocket.

Core (ship this first)

Rooms (public / private) and member JWTs
Realtime messages over WebSocket
REST send + history
Presence and typing (when enabled on the Worker)
Inbox / unread (useInbox)
In-room agents (@assistant) with Groq/OpenAI on the Worker

Hosted vs self-host

	Hosted	Self-host
Worker	`https://api.fluxychat.com`	Your `workers.dev` or custom domain
Auth	Clerk in the CLI full template	Your backend mints JWTs (`POST /auth/token`)
Agents	Same Worker APIs	Same, plus your LLM keys in `.dev.vars`

Not the JS CLI

Native SDKs (Kotlin, Swift, Flutter, Unity, .NET) live in the repo, not on npm. Vue/Svelte packages are not part of --full.

Next: Migrate from Pusher, create-fluxy-chat.

Migrate from Pusher / Ably / Sendbird

API mapping, auth differences, and history import patterns for FluxyChat.

Self-host one command

Bootstrap a local FluxyChat stack with wrangler D1 migrations and dev env files.

On this page

Core (ship this first)Hosted vs self-host Not the JS CLI