stream-react

/stream-react is the default web pack. It builds React and Next.js apps with Stream Chat, Video, Feeds and Moderation, and integrates Stream into ones you already have. Any web React or Next.js request routes here, and so does /stream-builder. For React Native, and for native projects, see the platform skills.

A feeds-based social app scaffolded by /stream-react

Example prompts

/stream-react scaffold a Next.js chat app with a sidebar of channels and a message view
/stream-react add Video calling to my existing Next.js app. I already have Chat set up
/stream-react build a feeds-based social app: profile pages, follow button, timeline
/stream-react audit my Video integration before we launch
/stream-react upgrade stream-chat-react from v13 to v14
/stream-react build a ChatGPT-style assistant on Stream Agents, with voice
/stream-react we're switching off Sendbird, replace it with Stream Chat
/stream-react restyle the chat to match this screenshot

Docs first

The pack doesn't write Stream SDK code from memory. Before it writes any, it reads the docs for the SDKs in play with getstream docs: the React SDKs for the client and UI, the Node.js docs for the backend routes, and the Agents docs for Stream Agents. Chat majors can differ deeply, so it pins the stream-chat-react major the project has installed and reads only that major's docs.

Setup

It binds the working directory to a Stream app with getstream init, which opens a browser for you to sign in, and writes the credentials with getstream env. A new app is Next.js with Tailwind and shadcn unless you say otherwise. It installs the SDKs the app needs, and never bumps a Stream major that's already installed.

Product configuration, such as channel types, feed groups and moderation policies, goes through getstream api. Those writes are app-wide, so it first runs getstream status to tell you which app they'll change, and asks before each one.

Building

  • Auth: a server route mints the user's token with the secret, which never reaches the browser. An app that already has auth or a token endpoint gets it extended, not a second one. Apps start at a login screen, with no hardcoded users or seeded demo content.
  • Clients: each client mounts once, at the app shell, and is created safely under React Strict Mode with the SDKs' own hooks, such as useCreateChatClient() (see Keep React strict mode on).
  • Components: it starts from the prebuilt components and customizes them through documented props and hooks. Feeds has no prebuilt UI, so it builds from the Feeds hooks. Apps land on a channel list, lobby or feed, and ask for the camera or microphone only on an explicit action.
  • Product quirks it knows: Chat reaction types and capability checks, the follow control a Feeds timeline needs, call-type settings that only apply to new calls, and Moderation that stays in the Dashboard rather than an in-app review queue.

Defaults it keeps

The prebuilt components ship features users expect, and the pack keeps each one on unless you turn it off by name: Markdown in messages, reactions, threads, and, for AI replies in a message list, the typewriter, stop button and AI state indicator. A design reference that doesn't show a feature isn't turning it off. When it overrides a component, it overrides the smallest slot that does the job and puts back what the default rendered.

Verify

Every build ends with a type-check, a build, and the app started and tried in two browser tabs as two users. It runs a check for each default it kept, and reports what it verified, what it didn't, and any default you turned off.

Audit an integration

Asked for a review, it audits read-only: it checks the code against the docs, reports findings and fixes only what you ask. A pre-launch review, or an app that livestreams, follows the router's integration review together with the React checks for Video and livestreams.

Upgrade an SDK major

It reads the upgrade notes for the installed and the target major in the versioned docs, applies them, then verifies the app as it would a new build. For Chat, it follows the migration guide for that exact pair of majors, one major per pass.

Match a reference design

Give it a screenshot, a Figma frame, or "make it look like WhatsApp", and it rebuilds the Stream UI to match. A named app without a reference, such as "a Slack-like team chat", is guidance on structure, not a look to match.

Migrate from Sendbird

It replaces @sendbird/chat and @sendbird/uikit-react with Stream Chat React in place, against a verified Sendbird-to-Stream mapping. Moving your existing data, such as users, channels and message history, follows the router's data-migration runbook. See Migrate from Sendbird.

AI assistants, support bots and agents

It builds ChatGPT-style apps and assistants inside an existing chat on the AI components of stream-chat-react: streaming replies, a thinking indicator, stop generating, reasoning and tool-call steps, tool approvals and generative UI (A2UI and OpenUI). The model always runs on a backend, never in the browser, and the pack picks the backend from what you ask for:

  • Stream Agents: the agent and its models run on Stream, for text and voice.
  • Your own agent process answering in a Chat channel, such as a support bot or help desk, with the Stream Chat AI SDK or LangChain.

If either fits and you haven't said which, it asks.

Other skills

The pack doesn't install third-party frontend skills. If vercel-react-best-practices or vercel-composition-patterns is already in the session, it uses them for general React work, and its own rules win for Stream code. For Next.js APIs, it reads the docs that ship with the installed Next.js version. The skill itself is at skills/stream-react/.