CopilotKit raises $27M, AG‑UI adopted

AI agent tooling is starting to split into layers — and that is the real story here. CopilotKit’s May 5 funding round matters because it is not just another “AI developer tools” raise. The company says it closed a $27 million Series A and that the protocol it created, AG-UI, is now adopted by Google, Microsoft, Amazon, and Oracle. That turns a small startup financing into a standards fight — one about how agents show up inside real software, not just how they call tools. (copilotkit.ai) ### What did CopilotKit actually raise? CopilotKit said it raised a $27 million Series A led by Glilot Capital, NFX, and SignalFire on May 5, 2026. The company builds tooling for “app-native” agents — basically, AI agents that live inside a product’s interface instead of running as a detached chatbot or back-office automation (copilotkit.ai)ority of the Fortune 500 and supports millions of agent-user interactions each day, though those usage claims come from the company itself. (copilotkit.ai) ### What is AG-UI? AG-UI stands for Agent–User Interaction. It is an open, event-based protocol for keeping three things in sync — the frontend app, the user, and the agent backend. In plain English, it is trying to standardize the messy middle where an agent streams updates, asks for approval, renders UI, reacts to user input(copilotkit.ai)erent problem from model access or tool calling. (copilotkit.ai) ### Why is that a separate layer? Because “agent interoperability” is turning out to mean more than one thing. MCP is about giving agents access to tools and context. A2A is about agents talking to other agents. AG-UI is about agents interacting with users inside software products. Those are adjacent problems, but not the same one — m(copilotkit.ai)face wiring. (developers.googleblog.com) ### Why do the big-company names matter? They matter because protocol claims are cheap until other platforms implement them. CopilotKit says AG-UI has been adopted by Google, Microsoft, Amazon, and Oracle, and its GitHub materials also list LangChain, AWS, Microsoft, Mastra, an(developers.googleblog.com)ing like a house format and starts looking like a candidate standard. (copilotkit.ai) ### So is this competing with MCP? Not directly — but yes, strategically. The cleaner read is that these protocols are stacking, not replacing one another. An enterprise app could use MCP to let an agent reach tools, A2A to coordinate with another agent, and AG-UI to surface the whole workflow inside the product. But once mult(copilotkit.ai)ve to pick how auth, permissions, observability, and UI state move across those boundaries. That is where “open standard” talk becomes architecture work. (copilotkit.ai) ### Why does “app-native” matter so much? Because most companies do not actually want agents living in a separate window. They want agents embedded in CRM screens, support consoles, internal dashboards, and developer tools — with approvals, forms, and visible intermediate steps. AG-UI is aimed at that exact surface. The pitch is that (copilotkit.ai)ad of black-box automations running off to the side. (copilotkit.ai) ### What is the catch? Adoption claims are still early, and “adopted” can mean anything from documentation support to deep production integration. The broader agent protocol market is also moving fast — A2A has official backing and Linux Foundation stewardship, while MCP already has strong mindshare in tool access. So CopilotKit still(copilotkit.ai) rather than just a popular developer convention. (a2a-protocol.org) ### Bottom line? This raise is really a bet that the UI layer of agent software becomes its own standard category. If that happens, CopilotKit did not just fund a product company — it put itself in the middle of the emerging agent stack.