Logan Kilpatrick: prediction

Transcript context

…So let's talk harnesses. It seems. I was just talking to Andrew Lee, who's the founder of Task the other day, and he said, fundamentally, everyone these days is building the same thing. They're trying to all build the general purpose drop-in knowledge worker. And so that's got to have the intelligence at the core, and that's got to have all this, he calls it the mecha suit that is built around it. So this harness sounds like the mecha suit that you guys are developing in-house. And I guess first question is like, Is this going to create silos? we've lived in this world so far where I could kind of mix and match my models and my infrastructure, right? I could go to LangChain or I could use Tasklet, I could use whatever, and I could pick whichever model and plug them in. But as they get more deeply co-trained with the harness, does this create kind of siloed worlds where you're kind of all in on one Frontier model company's stack or another? And if so, that would have pretty significant implications for kind of switching costs and stickiness and pricing power of the Frontier model creators. What's your take on how sticky things are going to get? It's a good question. I mean, I think Again, Chelsea probably knows better than me on this, but I think the best case is like you can do both. Like the best case is like it works really well for Gemini and sort of we can sort of do the things we want to do to scale up because we do have sort of control over the sort of full stack AI story as Sundar likes to say. But then also it generalizes across other stuff. Like I think the developer ecosystem, people want choice, people want to have flexibility in these tools. lots of use cases. Actually, there's like philosophical questions of how good really is your model if it can't generalize to sort of other harnesses. But I don't know how much. Yeah, I think that's the right, I think I fully agree. I think actually like maybe to double click on what Logan said originally, right? The benefit of the full stack that we have is we can hopefully build a really seamless experience. And you get the best of Gemini, you get it working in the most effective ways for you. get it working in a way that is intuitive, is smart, is fast. And so that also helps us then train the model to be better. So this becomes this flywheel that continues to power the model. At the same time, I think we don't want it to only be the case that the model works in a single harness. So we want any of our enterprise customers or a developer who's building their own use case to be able to leverage Gemini effectively. And so it is important then from a model standpoint that we're training in such a way that we actually, we sort of call it like harness diversity. We should be able to support a range of different approaches to tooling, to different approaches to orchestration, et cetera. But I think what's helpful about this approach of kind of co-training and building that flywheel, it's easier to debug. It's easier to think about data collection. It's easier to eval. You can just move at a faster pace. And I think we're seeing that across the industry. And so finding that balance is important, but I think it just helps build to make the model better.…

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