Rank #06 · Weekly

Rank #06 · Weekly · Infrastructure

AG-UI: The Agent-User Interaction Protocol

· Daily Top10 · License: MIT

Rank #06 Weekly — ag-ui-protocol/ag-ui

Give any agent a typed, bidirectional event stream so a web app, mobile client, terminal, or chat platform can render the same run.

  • Board: Rank #06 · Weekly ·
  • Repo: CopilotKit/CopilotKit
  • Stars / lang / license: 20,638 stars · TypeScript · MIT
  • License label: License: MIT
  • Data verified: 2026-11-20 09:04 Asia/Shanghai (official Daily Top10 gate; language/license confirmed via GitHub API get_repository + README + LICENSE + official docs)
  • Trending note: +3,455/wk (weekly Trending window; selection captured 09:04 Asia/Shanghai)
  • Tags: Infrastructure · agent-protocol · event-stream · TypeScript · MIT · generative-UI · human-in-the-loop · CopilotKit

What it does

AG-UI is the Agent-User Interaction Protocol: an open, lightweight, event-based protocol that standardizes how AI agents connect to user-facing applications. GitHub description: "AG-UI: the Agent-User Interaction Protocol. Bring Agents into Frontend Applications." Site: ag-ui.com. Docs: docs.ag-ui.com. Spec: docs.ag-ui.com/spec/1.0. Examples: dojo.ag-ui.com.

README and official docs (as verified):

License: MIT (LICENSE file and GitHub SPDX agree).

Who it's for

Less ideal if you only need a single-shot chat completion with no streaming, shared state, or mid-run user input, or if you want a hosted agent product rather than a protocol and SDKs to implement.

Stars / language / license

20,638 stars · TypeScript · MIT

Data verified: 2026-11-20 09:04 Asia/Shanghai (official Daily Top10 gate; language/license confirmed via GitHub API get_repository + README + LICENSE + official docs)

Trending note: +3,455/wk (weekly Trending window; selection captured 09:04 Asia/Shanghai)

Category tags

Infrastructure · agent-protocol · event-stream · TypeScript · MIT · generative-UI · human-in-the-loop · CopilotKit

How it differs from similar projects

Compared with a custom REST, GraphQL, or ad-hoc SSE API. Those can stream tokens, but every agent framework tends to invent its own event shapes for tools, state, and interrupts. AG-UI's pitch is a shared event vocabulary and generated SDKs so the client does not change when you swap the agent.

Compared with MCP. MCP connects agents to tools, workflows, and data sources. AG-UI connects agents to user-facing applications. The docs describe them as complementary layers; a single agent may use both. (On today's board, Firecrawl #01 and chrome-devtools-mcp #07 also expose MCP surfaces — different problem domains from AG-UI's agent-to-UI protocol.)

Compared with A2A. A2A is for agent-to-agent coordination. AG-UI is for agent-to-user interaction.

Compared with A2UI, MCP Apps, and similar generative UI specs. Those specify UI payloads. AG-UI is the runtime protocol that can transport them, plus chat, state, tools, and interrupts.

Caveats. Integration depth varies by framework; check the official list and Dojo demos rather than assuming every listed partner exposes every event family. Some example clients use hosted services (for example CopilotKit Intelligence in chat-platform samples) that are not part of the protocol. No independent adoption, latency, or compatibility audit is claimed here.

Repo link

https://github.com/ag-ui-protocol/ag-ui