TechPulseTechPulse
Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

75% Positive

Analyzed from 481 words in the discussion.

Trending Topics

#agent#chat#agents#sdk#github#open#source#slack#com#interfaces

Discussion (8 Comments)Read Original on HackerNews

opwizardx•7 minutes ago
Is it like a proprietary wrapper for Vercel’s Chat SDK (https://github.com/vercel/chat)?
mikeryan52•1 minute ago
Not proprietary and not a wrapper. Chat SDK served as inspiration, of course, but I think it misses a few hard parts of bringing agents to chat interfaces:

- Generative UI in these surfaces needs to be durable. If your agent composes a Block Kit or Adaptive Cards interface with interactivity, you have to be ready to handle that interactivity weeks later. We handle this with our JSX renderer.

- Chat interfaces are inherently multiplayer. The worst thing you can do is have your agent act like a bot: posting all of the time, creating noise, and offering no customization. I think Claude Tag nailed the user experience here, and now we want to empower developers to create agents with a similar UX via open source.

- Truly agent-and-surface agnostic. We're fully powered by AG-UI (ag-ui.com), so you can bring any agent into Slack and then take that same agent to web or mobile all over the same protocol.

chandureddyvari•1 minute ago
From quick glance I don’t think so that’s the case. copliotkit promises ag-ui compatiblity., which means it can work with codex cli, mastra, pi, claude agents sdk and other harnesses as well (there are ag ui adapters as well). I’m actually integrating this with claude agent sdk with ag ui adapter., which i don’t think is possible with vercel chat sdk.
chengyongru•44 minutes ago
I dont think it s really open source, the MIT part is just the client. The service that actually makes it run is closed and license-gated.
mikeryan52•32 minutes ago
Not necessarily wrong, but that's just a maturity problem on our end right now. We're aiming to take the same approach as our web SDKs: it works great for open-source deployments and works even better with Enterprise Intelligence. We had some back-and-forth over webhook vs. WebSocket in the last two weeks that caused some churn on our side.

If you point your agent at our SDKs, they should help you use the Slack or Teams adapters directly without leveraging the hosted service: https://github.com/CopilotKit/CopilotKit/tree/main/packages/...

Delivering AG-UI with generative UI to Slack and Teams should work great with the open-source packages. We'll make these interfaces better and more intuitive.

mikeryan52•about 1 hour ago
Hi folks! I'm one of the engineers working on the Channels SDK. This is our first public release. Our emphasis has been on making agents act like natural participants in Slack and Teams, while letting them generate UI along the way. It's built on top of AG-UI, so any agent that emits AG-UI can be brought to Slack or Teams.

We've been dogfooding this internally and have seen a surge of tiny, task-specific agents enter our channels. A lunchbot agent wraps the DoorDash CLI to handle office lunch orders, a pupfood agent wraps the Pup and GitHub CLIs to do incident triage, and a chadbot generates marketing videos on demand from GitHub PRs. We've got even more that compose PostHog, Notion, Linear, and other internal tools we use.

I had previously been pretty hot about bringing agents to the web, but I'm increasingly convinced that chat interfaces are the most natural home for useful agents.

Happy to answer any questions about our approach here!

wiradikusuma•about 1 hour ago
I saw WhatsApp listed but I can't find how the integration works?
mikeryan52•37 minutes ago
WhatsApp is only supported on the open-source side of the SDKs right now. Full support for WhatsApp in the hosted service is on the roadmap. Point your agent at github.com/copilotkit/copilotkit, where the Channels SDKs live, and it should be able to pick it up.