Baris Gultekin: recommendation

Transcript context

…How do you think about the question of, like, One big agent that might be long running versus the other kind of big pattern is your sort of initial agent that then routes tasks to sub agents. Back when OpenAI came out with their agents SDK, they had this notion of the handoff as a really central idea. And I was never quite clear on were they doing that because they thought that was the best way to maximize performance? Or was it more a nod to, we think at these enterprises that are going to use this thing, there's going to be different teams responsible for different areas, and we want to be able to modularize the work for human reasons as opposed to like for AI performance reasons. With Claude, on the other hand, and we have a sponsor of the podcast called Tasklet, which is a maximalist when it comes to just let Claude cook basically is their philosophy, give it everything it needs, let it make all the choices, let it run for as long as it can run, give it feedback, but like it's one long, one agent that kind of does it all in one long session. Of course, I'm sure you could say there's different use cases deserve different paradigms, but what do you see working the most in practice today? Yeah, even the Cloud Code case, you have skills that are being developed, right? So you're still modularizing the different kinds of things you want Cloud to do and then giving instructions for Cloud to do these things. I think the way you called out is what I'm seeing, which is in especially large enterprises, you have different teams building different agents. You also have different agent platforms that are being used. So for instance, if I'm using Salesforce to manage all of my CRM, maybe I'm going to go build my sales-related experiences with an agent there, but I still want that agent to talk to this other agent I'm building for something else. So being able to do that agent handoff and coordination is emerging. I wouldn't say this is necessarily super top of mind for everyone. I think still customers are focused on, let me get this one agent right and working well before I start thinking about multiple agents kind of coordinating with one another. But that's starting to become increasingly important. For customers, one of the biggest considerations is they do not want to be locked in to a certain platform. So they still want to be able to make sure that the, again, open standards are supported so that agents can talk to one another, agents can use the tools that you built for one agent by another agent and so forth. So MCP, A2A, these are important protocols that our customers expect to be supported. I was just going to ask about A2A. Are you seeing traction with that?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.