The outcome

Get into the official CopilotKit experience with the right account and a setup you understand.

CopilotKit is a open-source frontend framework for agentic chat, generative UI, shared state, and human-in-the-loop experiences. Building product-native agent interfaces with chat, custom components, shared application state, frontend tools, streaming, and deterministic human approval checkpoints. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Start at https://www.copilotkit.ai/ and confirm the domain before entering account or payment information.

  2. 02

    For desktop use, follow the official download link. Current availability: CopilotKit is installed into React or React Native applications and connects UI components and hooks to compatible agent backends through AG-UI..

  3. 03

    A supported web or mobile application, a compatible agent backend, a server-side model configuration, and an authorization design for every user, action, and shared state field.

  4. 04

    Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

  5. 05

    Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

Working standard

What good use looks like.

  • Use official download pages.
  • Review permissions during setup.
  • Keep installers and applications updated.

A polished interface does not make an agent action safe. Treat all client input and model tool arguments as untrusted, authenticate users server-side, authorize every resource and side effect, minimize shared state, keep provider keys off the client, use graph-enforced interrupts for mandatory approvals, make resumable actions idempotent, protect against cross-user thread leakage, and trace and test cancellation, retries, and partial failure.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.