CopilotKit v1.50 is coming soon!

Back
By Uli Barkai
June 2, 2025

We launched AG-UI one month ago, and it’s been incredible to see the reception and adoption.

Millions of views for content on AG-UI, tens of thousands of developers building and new contributions & integrations in the pipeline by some of the most important players in the space including Agno, AWS, LlamaIndex, Alibaba and more!

__wf_reserved_inherit

Discourse around AG-UI:

https://www.youtube.com/watch?v=BFWviieMyGw&t=382s

__wf_reserved_inherit

Recap on AG-UI

AG-UI is meant to help developers bring AI agents from backend processes that occur in the background - to interactive, key parts of AI native applications.

CopilotKit, has been innovating on this front for over a year, but AG-UI allows us to address this gap in the ecosystem in a far more powerful way, which will also bring immense positive externalities to the agent ecosystem.

MxN —> M+N

AG-UI serves as a bridge between Agents and Clients. Agents emit AG-UI compatible events as they are executing their workflow (one of 16 events), and AG-UI Clients read and interrupt these events.

Agent frameworks have to make simple changes, and they get full Frontend functionality right out of the box with Clients like CopilotKit.

But what is even better, that these frameworks will also receive support for any additional AG-UI compatible client created. There is already a team of contributors from AWS, creating a SMS/Whatsapp client with AG-UI.

This means that every AG-UI compatible framework, will get instant support for features by new AG-UI Clients. So your LangGraph agent will be able to receive human-in-the-loop feedback from WhatsApp, without LangChain having to implement this, and without the WhatsApp client having to implement LangChain support.

This means that instead of every client and every framework needing to collaborate, each just has to support AG-UI, and a world of functionality is unlocked.

Instead of M frameworks * N Clients, you have M frameworks + N Clients.

__wf_reserved_inherit

‍

Get daily updates-follow CopilotKit on Twitter @CopilotKit

Top posts

See All
AG-UI and A2UI Explained: How the Emerging Agentic Stack Fits Together
Nathan Tarbert November 19, 2025
AG-UI and A2UI Explained: How the Emerging Agentic Stack Fits TogetherThe agentic ecosystem is evolving fast — and with new standards appearing almost weekly, it’s easy to get lost in the terminology. Two names that often get mixed up are AG-UI and A2UI. They sound similar, but they actually serve very different purposes. Even better: they complement each other beautifully.CopilotKit has been working closely with Google on A2UI, and we’ll be shipping full support when the A2UI spec launches. But before that happens, let’s break down how these pieces fit into the broader agentic landscape.
Build a Frontend for your Microsoft Agent Framework Agents with AG-UI
Bonnie and Nathan TarbertNovember 11, 2025
Build a Frontend for your Microsoft Agent Framework Agents with AG-UIIn this guide, you will learn how to build a frontend for your Microsoft Agent Framework Agents using AG-UI Protocol and CopilotKit. Microsoft Agent Framework will power the AI agents backend, while CopilotKit powers the frontend, and then AG-UI creates a bridge that enables the frontend to communicate with the backend.
Microsoft Agent Framework is now AG-UI Compatible!
Uli Barkai and Nathan TarbertNovember 11, 2025
Microsoft Agent Framework is now AG-UI Compatible!We’re excited to announce that Microsoft’s Agent Framework is now fully compatible with the AG-UI protocol - the open standard powering frontend-agent communication across the ecosystem. This integration means you can now connect Microsoft’s powerful reasoning and orchestration layer directly to rich, real-time user interfaces - without custom socket code, polling loops, or one-off APIs.
Are you ready?

Stay in the know

Subscribe to our blog and get updates on CopilotKit in your inbox.