We're pretty excited for this one -- I think channels may soon become the 3rd big form factor of LLMs (after Chat, and Codex/Claude-Code style agents).

We've worked really hard to to shrink the onboarding setup to a single prompt:

"Read https://copilotkit.ai/channels-guide.md and help the user build their first channel".

It's literally that easy. Then it will help you create a coworker-grade Slack / Teams agent backed by basically any of the top agent frameworks and harnesses out there.

Would love to get feedback, especially if you hit any snags

Btw if you build a wingman AG-UI adapter the Channels SDK would just work with it. Nowadays, you can honestly get this done in probably less than a day of work --we've got a pretty good factory set up with validators and tests, etc.

Happy to help if interested!

Comments URL: https://news.ycombinator.com/item?id=48397786

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=48037265

Points: 9

# Comments: 0

AG-UI is a launch partner of A2UI, but it is a separate project by CopilotKit, not google.

We have a day-0 handshake between AG-UI & A2UI

AG-UI is built to support agentic behavior in your application, more similar to the Vercel AI SDK but horizontal and standardized.

MCP-UI helps external apps and APIs pass UI to applications, really well suited for use cases like Shopify stores inside of ChatGPT.

Comments URL: https://news.ycombinator.com/item?id=45994035

Points: 7

# Comments: 3

AG-UI is an open, lightweight, event-based protocol that standardizes how AI agents connect to fronted-end applications.

After a year of one-off, CopilotKit <> Agent frameworks collaborations, we decided to ship a standard, and open way for agents to connect to apps.

We are launching with day 0 integrations with LangChain, Mastra, CrewAI and AG2 with more partnerships on the way.

How AG-UI works: - Creates a unified, two-way bridge between backend agents and frontend apps - Works with any event transport (SSE, WebSockets, webhooks) - Supports 16 standardized event types for common agent-user interactions

Where AG-UI fits in the agent protocol landscape: - MCP: for agent←→tools communication - A2A/ACP: for agent←→agent communication - AG-UI: for agent←→human interaction in applications

We launched the protocol yesterday, and have been blown away by the reception. We have the first working group this Friday, to help expand and steer the direction of the protocol.

Check out the repo to get started!

Comments URL: https://news.ycombinator.com/item?id=43974484

Points: 36

# Comments: 5

Shipped this with cursor over the weekend and built: 1. The first web-based MCP client (deployed version on GH) 2. An open-source client you can add into any app.

Built using CopilotKit for the client and interactivity layer + agent frontend which connects to a LangGraph ReAct agent that coordinates MCP calls. Uses Composio's MCP server.

Comments URL: https://news.ycombinator.com/item?id=43322812

Points: 6

# Comments: 0

Co-agents help the user intervene at any step in the agent process / steer the agent. So the agent doesn’t need to be perfect to be useful.

Similar to the UX that Devin has but for any product.

We’re starting with LangChain / LangGraph integrations.

Comments URL: https://news.ycombinator.com/item?id=40915497

Points: 12

# Comments: 5

People use the same model / server for all queries not because it's sensible, but because it's simple. This brings the same simplicity to the far more optimal solution.

And great startup play too, by definition no incumbent can fill this role.

We are building CopilotKit = a framework + platform for building context-aware AI assistants into any application (not necessarily coding related applications).

Part of CopilotKit is about giving the Copilot / AI agents access to the application through a typed "inline realtime API". And to make ergonomics great for _our_ users, CopilotKit ships with hardcore type programming.

Cursor's Copilot (unrelated to CopilotKit) helped us write this type code (that's what went viral). And yes, GitHub Copilot is a mis-attribution.