AGKit vs CopilotKit
Choose AGKit when you want to expose application capabilities as tools while Cloud manages model bindings, profiles, credentials, and spending.
CopilotKit provides frontend actions, application context, state synchronization, and generative interfaces for its supported frontend stacks.
 AGKit | CopilotKit | |
|---|---|---|
| Application stack | Swift, Android, React Native, and Web; one Cloud backbone | React and Angular integrations |
| Application actions | Agent runtime, tool contracts, permission hooks, and cancellation | Frontend actions, context, and generated UI |
| Configuration | Cloud-managed model tiers, credentials, and agent profiles | Agent and backend integrations |
| Production controls | End-user identity, project/user budgets, and configured attestation | Framework and service-specific configuration |
| Application responsibility | Tool implementation, state validation, approvals, and actual undo | App defines actions and integrates its agent backend |
Choose your platform and access path for SDK availability and setup. Guard and confirmation support depends on the SDK execution path you integrate.
Where CopilotKit fits
Your product needs an agent-aware frontend with shared state, in-app actions, and generated interfaces. Its React and Angular integrations connect those experiences to an agent backend.
Where AGKit fits
You want to expose application capabilities as tools while Cloud manages the model bindings, profiles, credentials, and spending behind the experience.
What your team implements
You define what actions can do and when a change is safe to apply. Connect those actions to your state model, design approval, and test recovery when the user edits or cancels during a request.