docs: document chat platforms as an AG-UI client surface - #2324
Merged
Conversation
The Clients listings covered web, terminal, and React Native, which left the impression that AG-UI targets web applications. Add chat platforms (Slack, Microsoft Teams) alongside the existing entries, and state that a client need not be a web app because the protocol describes an event stream rather than a rendering target. The added text separates the layers: a chat-platform client is something anyone can build against AG-UI, the Channels SDK is one implementation, OpenTag is a readable application built on it, and CopilotKit Intelligence is named as a hosted service outside the protocol. No protocol, specification, or event-set changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Python Preview PackagesVersion
Install with uvAdd the TestPyPI index to your [[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
explicit = trueThen install the packages you need: # Core SDK
uv add 'ag-ui-protocol==0.0.0.dev1785940198' --index testpypi
# Integrations (each already depends on the matching ag-ui-protocol preview)
uv add 'ag-ui-langgraph==0.0.0.dev1785940198' --index testpypi
uv add 'ag-ui-crewai==0.0.0.dev1785940198' --index testpypi
# NOTE: ag-ui-agent-spec depends on pyagentspec (git-only, not on PyPI).
# You will need to install pyagentspec separately from its git repo.
uv add 'ag-ui-agent-spec==0.0.0.dev1785940198' --index testpypi
uv add 'ag_ui_adk==0.0.0.dev1785940198' --index testpypi
uv add 'ag_ui_strands==0.0.0.dev1785940198' --index testpypiInstall with pippip install \
--index-url https://test.pypi.org/simple/ \
--extra-index-url https://pypi.org/simple/ \
ag-ui-protocol==0.0.0.dev1785940198
Commit: 401e385 |
@ag-ui/a2a-middleware
@ag-ui/a2ui-middleware
@ag-ui/event-throttle-middleware
@ag-ui/mcp-apps-middleware
@ag-ui/mcp-middleware
@ag-ui/a2a
@ag-ui/adk
@ag-ui/ag2
@ag-ui/agno
@ag-ui/aws-strands
@ag-ui/claude-agent-sdk
@ag-ui/claude-managed-agents
@ag-ui/crewai
@ag-ui/langchain
@ag-ui/langgraph
@ag-ui/llamaindex
@ag-ui/mastra
@ag-ui/pydantic-ai
@ag-ui/vercel-ai-sdk
@ag-ui/watsonx
@ag-ui/a2ui-toolkit
create-ag-ui-app
@ag-ui/client
@ag-ui/core
@ag-ui/encoder
@ag-ui/proto
commit: |
mme
enabled auto-merge
August 5, 2026 14:38
mxmzb
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes PNI-271
Read the Clients listings today and you would conclude AG-UI targets web applications: they cover CopilotKit, a terminal client, and React Native. Nothing indicated that an AG-UI agent can serve a conversation in Slack or Microsoft Teams, even though it can. This is docs-only — no protocol, specification, or event-set changes.
Changes
docs/introduction.mdx— new row in the Clients table, same format as the existing entries. Two paragraphs under the table: a client need not be a web app, because the protocol describes an event stream rather than a rendering target; a chat-platform client is something anyone can build against AG-UI; the Channels SDK is one implementation; OpenTag is the worked example.docs/quickstart/clients.mdx(Get Started) — two sentences making the same point where someone building a client will read it.docs/integrations.mdx— one line in the Clients list, existing pipe format.README.md— row added to the Clients table.Register
No superlatives, no "any channel", no product voice, and no hosted-service call to action — the links go to the MIT-licensed repositories, not to a signup or trial page. Where a hosted component is involved the text names it as such: in OpenTag the agent and its runtime are self-hosted, while platform credentials and message delivery are handled by CopilotKit Intelligence, which is called out as a hosted service and not part of the protocol.
Notes for the reviewer
README.md:165), so the row went into the existing table rather than a new section.channels-sdk's repo description also mentions Discord and Telegram; the docs text stays with Slack and Microsoft Teams, which is what the SDK's documented path and OpenTag support today.prettier --checkflags all four files, but it flags them identically onmain. Pre-existing drift, left alone so the change is not buried in a reformat.Outstanding acceptance criterion: review for register by someone who does not work on Channels.
🤖 Generated with Claude Code