[
  {
    "startMs": 12960,
    "text": "Hello everyone. My name is Sarah, and I have a confession to make. So I've been using Datadog every day for the last six months, and the other day, my coworker comes up to me and he's like, \"Hey, Sarah, can I look at this alert?\" I'm like, \"Okay.\" So I open up Datadog, and I'm logged out. It's kinda awkward, so I have to log in, and he's, like, looking over my shoulder, and I'm, like, overly conscious about everything that I'm doing on my computer. And I open up the Data- the Datadog dashboard,"
  },
  {
    "startMs": 43680,
    "text": "and I just froze. I had no idea where anything was, and this is actually not a knock on Datadog. The problem was I had genuinely never opened the dashboard. I'd been using it every day without ever looking at it. And so today, I wanna make an argument that sounds kind of insane, and then show you that it's obvious. The dashboard is dead, and I think that's great news for everyone in this room, except probably for me, because I am--"
  },
  {
    "startMs": 73860,
    "text": "My team is responsible for the Composio dashboard."
  },
  {
    "startMs": 78840,
    "text": "Alas, how did we get here? I believe a postmortem is in order. Shall we? The year is 2022. It is the Dark Ages. Someone pings me on Slack. They say, \"Hey, I get this error when I try and search for prod.\" I would've instantly spawned five different windows, read the context in Slack, write a query in Datadog, check PostHog for this session, uh, fix the bug in VS Code, open the PR in GitHub. That is five tools and five UIs I have to learn and"
  },
  {
    "startMs": 108680,
    "text": "relearn every time they ship a new redesign. But frankly, redesigns are the least of my problems because every single tool has its own query language. So Datadog has its own query syntax, Jira has JQL, Search- Slack has its search modifiers. And it gets worse because even when these tools claim to speak the same language, let's say SQL, they don't even agree on SQL."
  },
  {
    "startMs": 135300,
    "text": "Every dashboard you've ever used, every weird, obscure query language ever written, was a translation device between you and your data because the machines on the other end cannot understand what you actually wanted. You never wanted a dashboard or its cursed query language. You wanted the answer. And in 2023, everything changed."
  },
  {
    "startMs": 157660,
    "text": "The sparkle button."
  },
  {
    "startMs": 160680,
    "text": "The sparkle button was born, and with a click of this magical button, an LLM would write a sometimes correct query to get you the answer you need. That is, if your question does not require more than two database joins."
  },
  {
    "startMs": 175480,
    "text": "And soon enough, these sparkling buttons were everywhere, so dashboards became AI native. Problem solved, right? Well, not quite. In November of 2024, Anthropic announced the MCP protocol with a promise to create an open standard for connecting AI systems with its data sources, and that it did. Instead of using a sparkle button, your own agent, Claude, whom you've already been using every day, could generate the query for you, execute it on your behalf, and give you the answer directly. And you might be thinking,"
  },
  {
    "startMs": 206600,
    "text": "problem solved, right? This is the end of the story. Well, far from it because MCP is a protocol. It's a channel for communication between agents and your service, and it's up to you, the service, to choose how to communicate with the agent, and it turns out that makes all the difference. If you've ever actually wired up a dozen MCP servers, you will know the reality is a mess for three reasons. Agents don't learn. Every conversation starts from zero. It has no memory of how it"
  },
  {
    "startMs": 236340,
    "text": "fumbled formatting links properly in Slack yesterday, and so it's just gonna fumble again today. And we patch this with skills, but skills is just a Band-Aid because agents become dumber with the more context you provide, and loading more tools, more skills, takes more context. And if you connect enough servers, you're dumping thousands of tool definitions straight into the context window. I mean, our GitHub, like, toolkit alone has over 200 tools. The model just drowns. It grabs the wrong tool or struggles to resolve dependencies, and it can't figure out"
  },
  {
    "startMs": 266340,
    "text": "which one it needs to call first. And third, every app is isolated. Each MCP server knows about itself and nothing else. So the moment a task spans two apps, and like they always do, it is your job to piece that together. And so MCP gave agents a door into every app, but it left them standing in thousands of separate rooms with no map and no memory of ever being there."
  },
  {
    "startMs": 294960,
    "text": "I'm gonna show you a mock-up demo here of how I would solve this bug report, uh, from the very beginning, how I would solve it in 2026. So imagine in this mock-up I have my Claude connected to the Composio MCP. What I would do is I would literally just copy and paste the link to the message from Slack and say, \"Please use Sentry, Datadog, find the root cause, create a draft PR, make no mistakes.\" And the first thing it does is it calls Composio's search to state the task it wants to accomplish. So"
  },
  {
    "startMs": 324940,
    "text": "in this case, it stated three. It wants to fetch Slack messages, it wants to search Sentry issues, it wants to search Datadog logs. And for each of these three, Composio returns not only the correct tools it needs, but actually a plan of how to use them. So for example, for Slack, you actually have to find the Slack channel ID before you can start querying for messages."
  },
  {
    "startMs": 346540,
    "text": "Now that it's armed with all the context it needs, it has a plan. It starts pulling the message from Slack to see what the user complaint was. Then it begins pulling from data sources in parallel, Datadog, Sentry, and it begins scanning the code base. Once it identifies the root cause, PR is up with a fix in less than five minutes. I didn't have to build a workflow or write a skill to teach it how to do this. This is literally just Claude using Composio's MCP. And it has become so much easier to do things this way"
  },
  {
    "startMs": 376832,
    "text": "that opening up Claude has just become like muscle memory for me to do literally anything. And the dashboards I used to open every day are becoming increasingly unfamiliar to me."
  },
  {
    "startMs": 387992,
    "text": "And the impact of designing for agents is measurable. So these are some early unreleased, uh, results comparing Composio against each app's own native MCP that's listed in the Claude, uh, marketplace. So it's the same tasks, it's the same model, and we see a clear difference."
  },
  {
    "startMs": 404572,
    "text": "But why? Why is this experience so much better than native MCPs? It's because at Composio, we are developing a brand-new interface specifically designed for agents. We translate messy, sparsely documented, ever-changing APIs from all the apps that you live in every day into something that agents really love to use. So we build on top of MCP, CLI, and native tools to deliver a cohesive, unified, and excellent experience for your agents that allows them"
  },
  {
    "startMs": 434532,
    "text": "to perform complex operations across these apps seamlessly. I'm gonna show you a more classic example of, like, what I usually use it for every day. So let's say I want to dig into some user data. I want to see the distribution of what vertical my users select during onboarding. I can simply just ask Claude. Claude will again run Composio Search. It will write a query in PostHog, execute it, nice and simple. There's my results. But what if I wanted to take this up a notch? So I want to"
  },
  {
    "startMs": 464552,
    "text": "look at that e-commerce section right there, and I want to see what toolkits they like to use. Toolkits is another word for apps we like to use at Composio.  So let's see if Claude can figure out how it can pull this data from Metabase, uh, given the user IDs in, in PostHog. So once again, it uses Composio Search. It queries the user IDs of those who selected e-commerce from PostHog, and it actually saves it without loading the full results into its context."
  },
  {
    "startMs": 496112,
    "text": "Then it makes some queries, uh, in Metabase to get the database schema, sample some data, get a feel for how things are structured. And once it's confident, it actually uses a very cool tool called Composio Remote Workbench to dynamically generate an SQL query with a regex string to search for all those user IDs, again, without ever loading the entire thing into its context window. And there we go."
  },
  {
    "startMs": 522472,
    "text": "So we can see the most popular toolkits amongst this user persona in less than a few minutes, uh, and that's data pulled from both sources. If you want to play with the live version, come visit us at the Composio booth. Uh, I'd love to have you play with this live."
  },
  {
    "startMs": 540012,
    "text": "And so the dashboard has died, and I'm thinking more and more about what this means for the future. Many startups have begun making their landing pages and their websites AI-friendly for GEO purposes, but so few have really prepared their applications to be used by agents. Composio began as a tool to help developers. We were taking these popular apps that users like and turned them into these tools that agents could use. But the humans are tired of dashboards, and their"
  },
  {
    "startMs": 569912,
    "text": "agents a-are tired of poorly designed MCP servers. And now we're getting requests from startups saying their clients are begging for a way to use their services through their agents."
  },
  {
    "startMs": 581612,
    "text": "So this is a lesson for everyone building anything right now. You are now serving a new species of user. They don't have eyes. They are not going to click your sparkle button. It shows up with a goal and a set of tools, and it judges you on exactly one thing, whether it can get the job done. For a decade, we've built pro-- uh, we've built products to be easy for humans to use, and the next era belongs to those that are easy for agents to use. So"
  },
  {
    "startMs": 611552,
    "text": "picture me again. I'm frozen in front of that Datadog dashboard, and I was thinking to myself in that moment that I'm falling behind. Uh, but now I think of that moment as a preview of what's to come. Thank you."
  }
]
