StackMap
Subscribe
Explore / ag-ui
ag-ui-protocol

ag-ui

AG-UI, the Agent-User Interaction Protocol: ~16 standard event types that stream agent runs into frontends — chat, shared state, generative UI, frontend tools, human-in-the-loop.

16,456 1,499 TypeScript MITupdated yesterday
agents
View on GitHubDispute this mapping →
Curator's take

Adopt it when you're putting an agent inside a real app UI and don't want a bespoke streaming format per framework — LangGraph, CrewAI, Google ADK, Microsoft Agent Framework and Strands already speak it, so the frontend stays when the backend changes. It's the agent↔user layer, not tools (MCP) or agent↔agent (A2A). Born at CopilotKit, whose React components are the smoothest client; a CLI agent with no UI gains nothing.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside ag-ui. Ranked by curator confidence.

pairs wellpairs wellpairs wellpairs wellpairs wellLangGraphCrewAIOpenBotharness-sdkaimockag-ui
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md2 min read

ag-ui Logo AG-UI: The Agent-User Interaction Protocol

AG-UI is an open, lightweight, event-based protocol that standardizes how AI agents connect to user-facing applications. Built for simplicity and flexibility, it enables seamless integration between AI agents, real time user context, and user interfaces.

ag-ui-protocol%2Fag-ui | Trendshift

Version MIT Discord

Join our Discord →     Read the Docs →     Go to the AG-UI Dojo →     Follow us →

1600x680

🚀 Getting Started

Create a new AG-UI application in seconds:

npx create-ag-ui-app my-agent-app

Useful Links:

What is AG-UI?

AG-UI is an open, lightweight, event-based protocol for agent-human interaction, designed for simplicity & flexibility:

  • During agent executions, agent backends emit events compatible with one of AG-UI's ~16 standard event types
  • Agent backends can accept one of a few simple AG-UI compatible inputs as arguments

AG-UI includes a flexible middleware layer that ensures compatibility across diverse environments:

  • Works with any event transport (SSE, WebSockets, webhooks, etc.)
  • Allows for loose event format matching, enabling broad agent and app interoperability

It also ships with a reference HTTP implementation and default connector to help teams get started fast.

Learn more about the specs →

Why AG-UI?

AG-UI was developed based on real-world requirements and practical experience building in-app agent interactions.

Where does AGUI fit in the agentic protocol stack?

AG-UI is complementary to the other 2 top agentic protocols

  • MCP gives agents tools
  • A2A allows agents to communicate with other agents
  • AG-UI brings agents into user-facing applications
The Agent Protocol Stack

🚀 Features

  • 💬 Real-time agentic chat with streaming
  • 🔄 Bi-directional state synchronization
  • 🧩 Generative UI and structured messages
  • 🧠 Real-time context enrichment
  • 🛠️ Frontend tool integration
  • 🧑‍💻 Human-in-the-loop collaboration

🛠 Supported Integrations

AG-UI was born from CopilotKit's initial partnership with LangChain and CrewAI - and brings the incredibly popular agent-user-interactiv