正在打开每日关注
正在打开每日关注
CopilotKit 以 AG-UI 为适配层,把同一 Agent 接入 Slack、Teams 等频道并渲染原生交互 UI。
Another blow to Anthropic! They spent months building what's now fully open-source. Anthropic recently put Claude inside Slack, where you can tag it in a channel. It reads the thread, breaks the task into steps, and posts the result back. The problem is that it only runs Claude and only in the channels Anthropic supports. Running your own agent there is harder. The reasoning, tool calls, and state management are mostly handled by the framework. Connecting that agent to a messaging platform is not. Moreover, each platform has a different integration: - Slack renders messages with Block Kit - Teams uses Adaptive Cards - and each has its own SDK, auth flow, and delivery model. If an agent needs to run on three platforms, one must write three separate integrations against the same agent logic. That overhead explains why most custom agents never get deployed to Slack, and why the ones that do are usually a single vendor's hosted assistant. The alternative is to keep the agent in one place and add a per-platform adapter that translates its output into each platform's native format. The agent is written once, and each channel requires just another output target instead of a separate build. CopilotKit open-sourced this full implementation in the Channels SDK. Essentially, any agent that implements AG-UI can run in a messaging platform in a few lines of code, like Slack, Teams, Discord, WhatsApp, and many more. Because the agent runs inside the thread, it has that conversation's context, so it can summarize the discussion, open a ticket, or route to the right person. It works with any backend, so LangGraph, CrewAI, Mastra, Google ADK, or a plain HTTP agent can connect through an existing endpoint. The same message can render as a Block Kit in Slack and as Adaptive Cards in Teams. In practice, the model and orchestration stay the same; it requires no migration or rewrite. It also handles human-in-the-loop approvals, persistence, and transcripts that carry state across platforms, so a thread started in Teams can continue in Slack. CopilotKit is open-source, and AG-UI is supported across every major agent framework, including LangGraph, CrewAI, Mastra, and Google ADK. Here's the repo: https://t.co/czi4hE192C (don't forget to star it ⭐) The agent running in Slack no longer has to be a vendor's. It can be the one you already built. The video below shows this in action. Thanks to CopilotKit for working with me on this launch.
🚀 Introducing the 𝙲𝚑𝚊𝚗𝚗𝚎𝚕𝚜 𝚂𝙳𝙺 Bring any Agent to any Channel. Slack, MS Teams, WhatsApp, and more. A significant jump from the state of the art across every dimension. With support for: → Generative UI → Streaming replies → User-based auth → Per-user learning Try it live: https://t.co/N3nIRDebKf GitHub: https://t.co/3Z185uYzkg
是什么 Channels SDK 是 CopilotKit 的开源 MIT SDK,目标是把 AG-UI 兼容 Agent 接入 Slack、Microsoft Teams、Discord、Telegram 等频道。Agent 保留模型、工具和业务逻辑,频道负责承载对话与结果;仓库元数据为 873 stars,创建于 2026-07-16,最近提交于 2026-08-14。
核心设计 它以适配器隔离平台差异:同一交互描述可转为 Slack Block Kit、Teams Adaptive Cards 等原生 UI。Intelligence 管理 Slack/Teams 连接和事件投递,用户运行长驻 listener 与 Agent;线程上下文、流式回复、文件、生成式 UI、人工审批、持久化和 transcript 组成工作流。README 的 OpenTag 示例是 Python LangGraph Agent 经 AG-UI 接入 Slack/Teams,并在 Linear/Notion 写入前请求审批。
关键洞察 价值在于把 Agent 执行面与渠道交付面拆开,新增平台主要增加 adapter,而非复制编排逻辑;截图中的 CSV 分析、GitHub issue triage、表格与优先级图表展示了自然语言任务到结构化产物的闭环。
边界与风险 它是接入基础设施,不保证平台能力完全一致。仍需 provider app、认证、项目 API key、长运行进程,并自行负责 Agent、部署、状态与日志;跨平台权限、状态和审批链应逐平台验证。