It's not just you. Let's take a small paragraph and break it down.
> Surface-agnostic APIs: Kai ships with an opinionated web application and a Slack integration, but the main primitive is the underlying API that powers them both. The agent is a service, not an application, and surfaces are simply customized views into it.
I...kinda get that they built an API that the agent polls. And then Slack or the webapp both invoke the agent? If so, the above paragraph is obscuring the point. Also, why isn't there a diagram showing it? There is a diagram below showing "Execution Environment" below, but that one doesn't show the API. And Kai and "Stripe Product Agents" are parallel paths on it. Does it not call out to this API anywhere?
I doubt if most people these days actually try to understand any of this, or just go "Agents? Cool! Here's some product that's vaguely similar that I like or have worked on!".
> Surface-agnostic APIs: Kai ships with an opinionated web application and a Slack integration, but the main primitive is the underlying API that powers them both. The agent is a service, not an application, and surfaces are simply customized views into it.
I...kinda get that they built an API that the agent polls. And then Slack or the webapp both invoke the agent? If so, the above paragraph is obscuring the point. Also, why isn't there a diagram showing it? There is a diagram below showing "Execution Environment" below, but that one doesn't show the API. And Kai and "Stripe Product Agents" are parallel paths on it. Does it not call out to this API anywhere?
I doubt if most people these days actually try to understand any of this, or just go "Agents? Cool! Here's some product that's vaguely similar that I like or have worked on!".