CopilotKit

Open-source frontend stack for agentic applications: generative UI, chat/runtime components, and AG-UI-based surfaces that can bridge web apps, Slack, Teams, and other frontends.

Current Source Snapshot

As of the 2026-07-01 registry refresh, @copilotkit/react-core latest is 1.62.1 and @ag-ui/core latest remains 0.0.57. The 2026-06-30 GitHub snapshot had CopilotKit/CopilotKit MIT-licensed with 35,648 stars and the repo description "The Frontend Stack for Agents & Generative UI." The latest GitHub release surfaced by the repo was bot-teams/v0.1.0, published 2026-06-25, matching the Open Tag / team-chat surface signal. Source: GitHub CopilotKit/CopilotKit, 2026-06-30; npm registry packument, 2026-07-01

What It Owns

Use CopilotKit when the product problem is an agent frontend, not only an LLM call:

Need CopilotKit fit
In-app React assistant Chat/runtime components and app-aware agent state
Generative UI Model-driven UI constrained by application components
Cross-surface agent AG-UI protocol plus Open Tag-style Slack/Teams clients
Human approval Reviewable actions before external side effects
Full thread context Agent behavior tied to the surrounding conversation or workspace

This sits between Vercel AI SDK and product UI. AI SDK is the natural default when Kevin is building a Vercel/React app with model streams, tools, and typed messages. CopilotKit becomes interesting when the frontend itself is the product surface for an agent: embedded copilots, collaborative workflows, or non-web clients.

Open Tag Signal

Open Tag is CopilotKit's early-access answer to "Claude Tag, but open and harness-agnostic": Slack and Microsoft Teams first, with Discord, Google Chat, Telegram, WhatsApp, web, and mobile signaled in replies and the intake form. The launch thread claims support for generative UI, streaming replies, human-in-the-loop approvals, and full thread context, built on CopilotKit and AG-UI Protocol. Keep implementation claims tied to current docs/repo state because the public product/API surface was still early access at the time of the bookmark. Source: X/@ataiiam, 2026-06-25

Boundary With Photon Spectrum

Photon Spectrum is adjacent but starts lower in the stack: message providers and agent reachability across iMessage/SMS/Slack/Telegram/WhatsApp. CopilotKit starts from agent frontend state, generative UI, and AG-UI-style control. Use Spectrum to get the agent into the channel; use CopilotKit/AG-UI when the product needs structured run state, generated UI, and approval semantics that remain consistent across channels.

Routing

  • Load copilotkit when a task mentions CopilotKit, Open Tag, AG-UI, generative UI, Slack/Teams agents, or "agent frontend."
  • Start with the repo/docs/package version, not memory; this stack is moving quickly.
  • Treat Slack/Teams/Open Tag as a product-client integration until public docs or code prove the exact API.
  • Pair with AI-Native Design Patterns and Human-in-the-Loop Control for UI/control requirements.

Timeline