Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Today we're launching Amplitude Custom Agents. Teammates that automate recurring workflows on your product data, 24/7. The signal your team needs already exists in Amplitude. Getting it to the right person, in the right format, before the moment passes still requires someone to do the assembly. Custom Agents change...

11,426 görüntüleme • 3 ay önce •via X (Twitter)

6 Yorum

Turner Novak 🍌🧢 profil fotoğrafı
Turner Novak 🍌🧢3 ay önce

This is awesome. So much cool stuff you can build with this.

mrs. robot profil fotoğrafı
mrs. robot3 ay önce

@TurnerNovak love this!

Arya Shah profil fotoğrafı
Arya Shah3 ay önce

Imo the real moat here is the system-of-record write layer. Analytics are great, but executing in jira/slack has the most value for teams

Shaun Gold | Venture Comedy profil fotoğrafı
Shaun Gold | Venture Comedy3 ay önce

Finally, an agent that creates tickets instead of creating another meeting about creating tickets.

Ferbin profil fotoğrafı
Ferbin3 ay önce

cool's not shipping. what's actually hard to productize?

Timur Yessenov profil fotoğrafı
Timur Yessenov3 ay önce

Product-data agents are a good wedge because the input already has ground truth. I’d start with one recurring decision: which churn signal becomes a Linear ticket, who owns it, and what evidence from Amplitude must be attached before anyone acts.

Benzer Videolar

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: (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.

Akshay 🚀

244,387 görüntüleme • 2 ay önce