The usual first-run snags, and why each one happens. If something here doesn't match what you're seeing, the Watch panel will show you the session's actual state.
The button never appears.
The CoworkkitProvider isn't mounting. Three common causes: it's not wrapping your app, it isn't in a "use client" component (getToken is a function prop, so the Provider has to be a client component), or you've set intensity="off". The Provider needs to wrap your tree in a client component with a working getToken.
The agent connects but is silent.
First check your token route: it must return HTTP 200 with a JSON body of { token, serverUrl, cloudUrl } — a 4xx/5xx or a missing field leaves the agent with nowhere to speak from. Then check you allowed the microphone. Finally, if the browser blocked audio autoplay, the SDK shows a one-tap "enable sound" affordance — click it and audio resumes.
The button shows "No answer".
The session connected but no agent joined the room, so the button reports No answer rather than looking ready and doing nothing. This is almost always transient — the agent for your workspace was momentarily unavailable. Retry in a few seconds; if it keeps happening it's on our side, so get in touch.
The microphone is blocked, or I get no permission prompt.
The mic needs a secure context. It works on localhost and on any https:// origin, but the browser refuses getUserMedia on a plain http:// LAN IP (e.g. testing from your phone against http://192.168.x.x) — serve that over HTTPS instead. When the prompt does appear, allow the mic; an earlier "block" sticks until you clear it in the site's permissions.
npm install @coworkkit/react 404s.
During the private preview the packages are delivered through private git repositories, not the public npm registry — a bare install by name won't resolve yet. Install from the git repos instead (your onboarding grants your project access):
npm i github:emirsafian/coworkkit-react#v0.4.0 github:emirsafian/coworkkit-server#v0.4.0My environment variable isn't picked up.
Restart the dev server after editing .env.local. The server reads env vars once, at start — a value added or changed while it's running won't be seen until the next boot.
It worked, then the agent stopped after a while.
Sessions idle-cut after a stretch of inactivity to save cost — see the session lifecycle. Nothing's broken; click the button again to start a fresh session.
Which browsers are supported?
Modern Chromium (Chrome, Edge, Arc, Brave), Safari, and Firefox — anything with WebRTC and microphone access. There's no plugin or extension to install.