Anthropic's Katelyn Lesse & Angela Jiang: Building an Ecosystem, not a Walled Garden

The last layer of abstraction on top of this is probably the coordination layer. So you have knowledge and you have execution and you have coordination. And at the coordination layer, we're beginning to think of these things called like strategies, where basically it's almost like a meta harness. The true low level harness is designed for execution. But the next one is about, okay, if tokens aren't really fungible and you need to give them different jobs, like maybe this token is advising versus this token is executing, you want to start composing these kind of orchestrated strategies that go together. And they should sit on top of all these things because at the end of the day, you still need to execute and the execution still needs to know what to do. So everything in theory should kind of like ladder together. And so I think, you know, if you were to look at our roadmap and maybe kind of project forward a little bit where you kind of expect us to go, we'll move more and more from the knowledge layer to the execution layer, from the execution layer to the kind of coordination layer in terms of the abstractions that you can see us put out. Caitlin and Angela, thank you so much for joining us today. Lauren and I are thrilled to have you here. You are responsible for building Anthropix platform. And so you are responsible for building what I think is one of the most important, if not the most important developer platform in the world. And we are really excited to interview you today to understand more about what's ahead. And so maybe just to get started, can you give us the context of, you know, what is Anthropix platform and where do you sit within Anthropix? Yeah. So platform. Platform is both our externally facing APIs, our developer platform that people build on top of when they want to build applications and systems that access Cloud's intelligence, as well as internally, we run our product infrastructure. And basically, we're the layer that our apps build on top of internally as well. Awesome. What's your North Star as a team? It's a great question. We actually, because we have both internal and external, we actually kind of have like two North Stars, which is probably like, you know, you'd be like, why? There's only one North Star. There's only one North Star, but no, we have a different planetary system. Yes, exactly. There's separate solar systems, so it's fine. But on the internal side, like we really want to provide is like literally as much leverage as possible for our internal teams to be able to ship like AGI-pilled products. And we want them to be able to move fast, be able to have reliable, like great, like platform to be able to build on top of. But I think that key bit about speed is like really intentional for us. And we really, really care about that internally. Externally. We actually have a lot more like complicated set of things. But one of the true Norths that we have there is to be able to basically give any builder the tools to be able to work with Claude to build whatever they want to build. And so it's a bit of a broad statement, but as a result that boils itself down into, you know, being wherever that business is, like we really care about like bringing our platform really, really close to that business. This is why we spend a lot of time with the hyperscalers and integrating really closely directly with them, like AWS, Google, so on and so forth. And it is a lot of like primitives that we end up creating. We want people to be able to express what they think their product should be. We want them to be able to almost do like custom software in their own way. You know, like in this new world with AI, what used to be probably economically impossible was that last mile of custom software now, in theory, should be like very, very achievable. And we want to give them all the tools and all the capabilities to go and do that. And so sometimes that comes in the form of primitives and APIs and higher order abstractions, and sometimes that comes in the form of just like standards. So, for example, like skills and MCP, those are things just like Cloud needs them to be useful. And we can just give them out to the rest of the ecosystem, work with everyone to help you create those things and get the best out of Cloud. So I would say externally, you know, we really are oriented around just helping you just be able to build. But internally, that orientation, while still existing, is probably more, you know, specified towards speed and being able to move really quickly. How do you decide what goes into the platform? What gets externalized and what doesn't to decide what products should be available? Yeah, I mean, we generally try to have a philosophy that we try to be consistent across the board. It's actually one of the reasons why we do internal and external. There's plenty of other, you know, platform businesses and constructs where you actually like bifurcate these two things. For us, we kind of try to intentionally keep it equal. And then as a result, we try to hold this philosophy as much as we can around like, you know, for any builder, internal or external, even though for internal builders might have some slightly different requirements in the same way. Usually would have slightly different requirements. We want to have the same primitives that are available to everyone. And one of the maybe the overarching thesis for that is that we've just seen, like, the capabilities of these models just grow and that's just exponential. And it's really hard to figure out, like, a long lasting form factor. I think two years ago, we were all like, everything's chat. And now everyone's like, forget chat. And it's just like agents. And like, there's going to be another form factor, another form factor. And we kind of imagine that, like, constantly evolving. And so the best way for us to kind of enable that for everyone and also ourselves is to actually build a really robust platform that gives people those kinds of like tools to figure out what those form factors are. And I don't think we by any means feel like we're the only ones capable of figuring out that form factor, like not at all. In fact, the more democratization we can do on that and help people and allow people to experiment, I think the more those form factors will actually kind of naturally come out of the market. Yeah. And I think within our team, we've we've had moments where we're experimenting even with just like a packaging up of our primitives in a different sort of higher order way. And we've thought about, OK, cool, we've solved this. We've solved this exact type of problem with this product that we've built into the world. And so we can go and dog food it for ourselves. But we'd never want to fall into this trap of like we're over indexed on the problem as it needs to be solved for an internal user. Like because exactly what Angela said, internal users have very specific requirements. External users have very specific requirements. And so if you over index on one or the other, you fall into a trap. So a lot of the time what we'll do is dog food something internally at the same time that we open up early access of some sort with external customers so that we can kind of get a range of feedback and bring those things back into the platform. I'd love to talk about the higher levels of abstraction that you discussed. So I guess at the base level, this is just, you know, raw access to Clive, Opus or whatever tokens. How do you think about the I guess the layer cake of abstractions above that? Yeah, if you look back. So when I joined Anthropic around a year ago, the platform was basically just the messages API. It was a messages API. You know, we had come out with standards like MCP. We obviously have developer tooling around our SDKs and our docs and our console and things like this. But for the most part, it was a stateless API. And what's interesting to Angela's point on form factors evolving over time is we found a lot of our customers solving the same problems over and over again that we also were solving over and over again around as the models got better at running for longer and working with more context at a given time. You want to build agents that can succeed in a kind of long running context and even a remote environment. And so we found that we could piece together our primitives and stand up all the same infrastructure that we're finding ourselves standing up internally to power our own products and arrive at some higher order abstractions that let you do more agentic work out of the box. And the problems that we're solving for you are, you know, infrastructure being kind of a hard thing to deal with. Like, how do you figure out spawning sandboxes that are going to have the right governance and security and like, you know, spin them up and spin them down? When you need to or the storage around transcript sessions so that you can resume a session if you stop it and pick it back up later. So that infrastructure is a big thing that we wanted to be able to provide more of out of the box. And we do more of that today. And then the second thing just being harnesses and harness engineering. There's a lot of thought and energy going into how do I do my prompt caching and how do I manage my context window as well as how do I actually just get more intelligence out of the model and how do I manage my costs and things like that. So. We've kind of packaged up our primitives a bit more in tune with the problems that we found ourselves solving to provide more of these things out of the box for people so that they can, if they're building systems for themselves internally, if they're building products, they can just be more focused on the problems that they want to be solving. And if they want to offload some aspects of those problems to us, they can. And that's kind of the ethos. And are your customers generally choosing to opt from the grab bag of stuff that you offer or are they like how often are they opting into the just the. The managed agent's offering, I guess, just take care of it all for me. It varies by like the the user group. So like for I would say, you know, like really AI native startups, like the ones who are like tinkering and like experimenting at a really low layer, they're just going to go for the primitives. And then for everyone else, these kind of classic like more like enterprises or areas where it's like the purpose of the startup or the philosophy behind the startup isn't necessarily to optimize on some kind of hill climbing pieces, more like stringing together a bunch of workflows and, you know, providing unique user value. And then for those people, you know, it's just kind of not their core competency. It's not where they want to focus their time and resources. And they reach much more for these kind of like higher order like package offerings. What are some examples of the primitives you've released at different layers in the last few months? We've seen a few of them. We'd love to hear. Yeah, I think maybe one framing I would give for some of the constructs that Caitlin was talking about is like and this is a bit of an oversimplification, but effectively there's approximately like three layers of this cake at the very bottom is just kind of like. And so at this layer, like in many ways, it's knowledge about the model, it's knowledge about the things that the model needs, and it's just like the ability to know how to actually do something with Claude is maybe the way I'd phrase that. And so there are the primitives that we have spent more and more time on have been actually things of the past because like we still evolve them, but they tend to be a little bit more baked. Like, for example, there's very specific shapes and parameters we put on the messages API, and it's more like trying to expressly like showcase Claude's like design. design, like Claude the model's actual design, the way it thinks, the way it respects certain parameters, the way it kind of like will do tool calls, like all of those different pieces. And then we started standardizing like tools and then we started standardizing bits and pieces of like context that you could put in at different moments in time, which is concretely like skills and like memory. And so those are like the kind of like knowledge layer type of abstractions that we've put out over the past, I guess like year plus a bit. The next layer of abstraction that we've actually started to spend more and more of our time on is like once you kind of know stuff, you then need to like execute. And so at the execution layer, that level of abstraction is the part that Caitlin was talking about around like we're doing these like higher order pieces, but like what are we putting higher order to there? It really is because you're now getting Claude to execute work. It's not just to know something, right? I can give it a question and give me an answer. You can string a lot of that stuff together. But now if you need to execute, like do work, give me the output, edit files in a bunch of different systems, that becomes a lot more complicated and requires infrastructure to handle. And so that layer is basically, I would say a low level harness plus managed infrastructure as like the set of abstractions. Today, we just like our high level product for that is called Claude Managed Agents. And so that's like a piece, but we started to wrap more and more pieces in that. I think there's going to be a layer like on top of that. We have like some inklings of it that we started to build towards, but the last layer of abstraction on top of this is probably the coordination layer. So you have knowledge and you have execution, you have coordination. And at the coordination layer, we've started to expose some of these in ways that like aren't very obvious, but we're beginning to think of these things called like strategies, where basically, it's almost like a meta harness, right? The harness, the true low level harness is designed for execution. But the next one is about, okay, if tokens aren't really fungible and you need to give them different jobs, like maybe this token is advising versus this token is executing, this token is dreaming versus this token's executing, so on and so forth. You want to start composing these like, these kind of orchestrated strategies that go together and they should sit on top of all these things because at the end of the day, you still need to execute and the execution still needs to know what to do. And so I think, if you were to look at our roadmap and the maybe kind of project forward a little bit where you kind of expect us to go, we'll move more and more from the knowledge layer to the execution layer and from the execution layer to the kind of coordination layer in terms of the abstractions that you can see us put out. That's a really cool framing. How do you think this all comes together into a broader ecosystem beyond just the things that you guys are building? How do you help support people building products on top of it? And how do you help them get the most out of all these pieces? Yeah, I think this is like super top of mind for us. Like we really want to, find a way to be, to support as many people in doing this as we can. I think we're still like learning. Like a lot of the industry like has evolved. We've seen, you know, a lot of different pieces get spun up and spun down. And I think the operative part for Caitlin and I has been in the category of like making sure, at least at the base layer, that we provide as many primitives across the board as possible. So, you know, this kind of like, yeah, like knowledge, execution, coordination layer, we want to give all of that out to everyone so that people can, start to compose and create on top of that. And that's just from a, I think, pure builder kind of point of view. Then there's a point of view around like, how do you kind of like plug in with us, right? Like we're also building first party products of our own. We've also created some ways to embed natively with us. Like for example, connectors, which are built on top of the MCP spec. And we try to be more open about those types of things. And we're starting to figure out like, what are the right bits and pieces? But what we're really trying to do is get to a place where, you know, a company is able to get created and built on, they can build whatever products that they want. They can build agents if they need to. And then those agents and those products could be things that can plug into other agents. Some of those agents could be cloud agents. Some of those agents could be other people's agents. But we want to be able to enable that kind of like, transactability across the board. And then I think in order for all of that to kind of ultimately be true, there is a bit around like standard setting. And I think there's the traditional standard setting, which is around, you know, how do systems interoperate? And that's, you know, things that you've kind of seen us do with like skills and MCP. But they're out again, like the builder layer. I think at a higher order layer, there's also a bit around interoperability and standard setting around, how do we all kind of like treat safety together? And, you know, we've talked to a lot of these companies and this is less from, you know, philosophies aside, just more like no one really wants to have technology that's like, for example, like doing negative things on their service, right? So cyber, I think is a great example of this. You want to protect your own systems from like negative actors or bad actors. And so like, these kinds of like standard settings of like how can we find ways to partner with more and more people to be like, yeah, we all kind of want to make sure our critical infrastructure is good. We all want to prevent like fraud or any of those things from happening. And how can we work better with each of these members? I think on the last layer, we're still kind of like, we're still evolving. And I think we're still very much like trying to find ways that we can be better and work with the rest of the industry to bring people along and work with them. But those are kind of like, you know, the higher order primitives or pieces that we wish to kind of, like, be in place so they can work with folks to ultimately solve this. I think if I were to like take a step back at the end of the day on all of these things, you know, like this technology is so transformative. And if it's a little bit like electricity in a sense, like before electricity, there was just like, you know, you had to like have a candle and it was like, you can only do so many things. But with electricity, the reason why it's such a transforming technology for all of us and so greatly of a utility is because you can actually like wired it into everything. Everyone is able to actually, we can actually access it. We also have like standards and ways to plug in and do all the pieces that we need. And that's not something that anybody can do by themselves. They always have to work with the ecosystem and work with partners to figure out a path forward. - How do you think about the philosophy of building an open ecosystem versus a walled garden? And, you know, how do you think about what products are really important for you to own first party versus where you're perfectly happy to plug into other components of the ecosystem? - Yeah, there's, so maybe in using Angela's kind of layer, I think that's a really good question. I think that's a really good question. So what might be awesome for one year's worth of AI development will probably not be awesome for the next year's worth. And we just kind of try to have that mentality. We tell the team, just overall, around Anthropic, everyone's always trying to be like, is this AGI-pilled enough? And we also have this mentality of we built something, it works, it was cool for a year, and maybe it's not the right next thing. And so throw it away, try again. And we tell platform users the same thing. I just think that's probably just attached to the technology. So yeah, one principle is trying to always constantly find this new form factor. So sometimes we'll launch products in certain areas to try to showcase a new type of form factor. It's not necessarily because we think it's like the biggest ham or the most important thing to go after. But sometimes we're like, OK, this has always been a really difficult thing. And people have always communicated this way or tried some things this way. And can we show that maybe there's a slightly different way? And because the model capabilities are so advanced now, can we try to express it a bit differently? What's an example of that? Yeah, you know, like, cloud design is a little bit of that way. I think depending on how you squint, you might see it as a way that we are going into design as one of the verticals. But more often than not, it's like if you take a look at what we're trying to do with that product, there's a couple of decisions that were made in there. The first one is that you can actually try to offload more and more and more to cloud. And so it tries to be kind of opinionated on just talk to it and let it really try to figure it out. And yes, you can still edit it and do these kinds of things, but kind of discourage a little of that and more just like, just talk to cloud to go figure it out. The second thing was it was really trying to express that actually code is a way to solve for things that you wouldn't normally think would be the way. So a lot of people who have built generative slide decks or designs or whatever will pick the way of they have some kind of design system. You integrate against design system. It's almost in the traditional classic WYSIWYG style of designing something. And with cloud design, it was like, OK, can we try to just use code? Purely have cloud generate that code and would it like do a good job? And we found through some experiments early on, it's like, actually, it looks like it can kind of do that. And how can we kind of showcase that to the world? So that's like an example. We have a lot of other internal projects. And this kind of falls in the category of like expressing form factor. We'll all try it out internally. It'll be super cool for like two weeks. And then we move on to the next thing. We never even ship the thing, frankly. But yeah, we actually do a lot of product experimentation in that area. And that's like our labs team. And then there's like the second category, which is that we I actually do look at Tim like we're a business. we do look at TAM, we do look at areas that we think there'd be reasonable agentic operations that would happen. In those areas, we do tend to have an orientation towards things that are more token heavy. And by token heavy or token hungry, maybe is the way I would say that, is what we mean is once you spend one turn, you look at the end of that turn and you say, am I done? Or am I actually so glad that I did that thing? I want to do more of that thing. We like industries where it's like the answer to that question, you say, I want to do more of that thing. So coding is obviously the one that we all know. And the great thing about coding is that what it's actually doing is that once you've finished a turn, you look at that and you're like, that was incredible. I'm unlocked. I'm going to do more. I'm going to build more. I can do more. And there's other services where it's like, actually, when you finish that turn, you completed the job and you just move on. You know what I mean? And so we tend to go into the ones that are a bit more like there's this iterative flow. You're going to build more, generate more together. And then the last angle that we kind of take a look at is just sort of like, you know, there's going to be certain business functions that we're like, they are the buyer that we like to go to. We want to help them optimize their workflows, help them create better products there. And I think we've been pretty transparent with some of the verticalization, like we've done like finance, we've done like legal. And we've tried to kind of like narrow on into specific areas where we feel like by having the right context and the right tools and putting it together in a good form factor is probably useful for us to be able to do. And in each of those areas, we do, we're trying to do a bit of like showing the art of the possible across all the different ways that you would accomplish those outcomes. And so for, you know, like finance, for example, is a good one. You know, we, you could be a company that solves problems in finance and you could build directly on the messages API and you can just get some tokens and you can build everything else on top. Or you could be someone who builds on cloud managed agents. You can get a lot more out of the box. Or you could say, I'm going to build a plugin that are like a connector, right? That's going to sit within one of our products and within those form factors. When we did recently, we launched like cloud for financial services is like, okay, cool. We've got packages of skills and things like this. You could choose to use within our product, within other people's products. We even launched like cookbooks on here's how you would use cloud managed agents to go and do these things. And so I think for us, it's all kind of an experimentation around like, you know, we provide people all these different pieces and see kind of where they run with it. And then sometimes we put together products that are just packaging of all of these things. Like cloud tag, I think is a really good example. Like we had been seeing people in the industry go and say like Shopify did this with river, um, square block recently did this with builder bot. Um, there's like a few of these examples where people said, I'm going to, I'm going to build like an agentic platform internal to my company and I'm going to try to give it all the right context and I'm going to make it accessible from slack or from various other, um, you know, platforms that you'd want it to be accessible at. And so I think the cloud tag was very much a packaging of all those same things that anybody could choose to build something similar, but this is how we're kind of like, well, this is how we're doing it internally. And if you would like to just kind of plug in and go, here's what that looks like. What do you think people misunderstood about cloud tag? Cause there was all this like ruckus about, Oh my gosh, it's just a slack bot. Like tell us what the magic of tag is. No, I think it's a great question. Um, and I do think it actually showcases a little bit of where maybe the future could be going. Um, yeah, I think like the, I think if you look at products in the past, people are like, Oh, you really attached to like the form or the, the UI almost, right? Like it looks like this. So it's like super cool. Um, and I think when you look at like tag, uh, it like, yeah, like the way you interact with it is that you like literally tag it in slack. Uh, and so, yeah, that is like the interface, but that's not really the important part. The important part, um, is all the kind of like context engineering and like architecture that we've put underneath the hood. So that tag just works. It really should, it just like, just feel like a coworker, like a co you know, if you go to a company and you onboard the coworker comes into your channel and then you can chat with it, it's proactive. It figured out like what's like useful and, um, it just gets stuff like done for you. And so if you think about, you know, especially like non-technical audiences, this is like, it's a huge unlock. You just, you literally create a channel and then you add cloud or sometimes you don't even add cloud and you're like, Hey, I want to be able to do this and do that. And I can't figure out this. And how do I actually like submit an expense report again? And traditionally, do you think all of that workflow, you are going all over the place and you're talking to your manager and you're talking to your spin up buddy and it's really, really complicated. And, uh, today now you just like go talk to cloud tag and we do a lot of the hard work on doing the context engineering, the proactivity, a lot of the harness pieces. I think Andre Caparti said it really well. It's like, it's like an org level harness. There's a lot of like complexity baked into that. Like Kayla mentioned, like you can use our APIs to go and construct that. You can do a lot of the experimentation yourself, obviously, but this is like an opinionated take from Anthropic on like this really awesome, always on a kind of agent for your entire, entire company. And the bit that's like futuristic, I guess, is like a lot of that complexity is actually like, it's like an iceberg. It's like all the stuff underneath it that's actually becoming the harder and harder and like useful part that we're trying to like push through. And I think we'll see more and more like that kind of like tip bit that's like outside in the water. It's just like the interface can actually constantly swap. Like today, right? Like Slack is a place where a lot of people collaborate, a lot of business collaborate, but also a lot of people collaborate in teams. And some people collaborate by a WhatsApp group or they text each other, or they may, some people still email each other. And like, those could be the form factors that actually completely, you can imagine agents just going there and being, and they're almost taking up the same form factors as humans have taken up. It was almost like a very, almost like boring take, but it's actually like, I feel like the most like forward one, because you want the agent and you want AI to basically be like another person. And it's helping you but it's like, you know, very intelligent, can figure out all the context and you can always have it to be a really helpful assistant. Totally. You talked about context and then harnesses quite a bit. And so your team is just, you know, has such an opinionated point of view on like what it takes to build an exceptional agent. I imagine a lot of that comes down to the context engineering and the harnesses. Totally. Maybe like what best practices or advice would you, would you share with people about what you need to get right on the harness and what you need to get right on the context? Yeah, I think so. It's interesting because, we've kind of talked about, you know, we launched Cloud Managed Agents as this like very generic, but high performing harness, because we've done all the nitty gritty work that's actually like really boring and not super interesting around how do you deal with prompt caching? How do you deal with context management? You like clear old stuff out of the window. Sometimes you like call tools programmatically, so you don't pull everything into the context window and you can keep it clean. There's a lot of those sort of details on the lower level harness layer. And I think honestly, like best practices are just stuff like prompt caching, do it. You're gonna save a lot of money and token costs. Obviously like try to keep your context window clear and then putting those things together in a harness that will be performant is, you know, sometimes specific to the tasks that you're trying to accomplish, right? And then of course evals. I'm surprised we got this far into this thing before one of us said the word evals, but like you need evals to make sure that what you're trying to accomplish is going to be the best that you can get right on the context. But I think we're starting to go, and Angela mentioned this a little bit earlier, is more of a concept of strategies or meta harnesses. Because I do think that, yes, you can, again, make this lower level harness that's going to be performant and maybe that's interesting for you to do yourself or maybe not and you offload it to us. But this concept that you can take any given token and spend that token on just executing or you can take that same token and choose to actually reflect on your past agentic sessions and write learnings to memory so that the next agent does a good job. Or you could take that token and advise with a bigger model so that a smaller model can execute and do a better job. Or you can say execute, execute, and then like a grader comes in and is like, did you do a good job? No, you didn't. Try again, right? And so I think the interesting innovation is going to come more at that higher level on the meta level, right? And I think optimizing within those strategies is something that I think is going to be really important. And I think that's something that our team is really excited about. And we're starting to do a lot of work there. And I think a lot of other people are starting to feel really excited about this concept of strategies and like the jobs you give to tokens. Because again, like, yes, there's best practices on stuff like your problem caching and exactly how you clear stuff out of your context window and how you write your evals and like a lot of things like this. But I don't know that there's necessarily so much juice to squeeze in a lot of cases out of that layer as compared to a layer higher than that. Yeah. And one of the reasons for that, I think, is it has to do with the generations of the models. If you look like two years ago, a lot of the harness was like a scaffold to kind of like, tell the model to go from point A to point B. And you had to like, you really had to like build in a lot, you'd have practically built one wall here and one wall here, sort of like the thing would go in a straight line. And now the models are actually very, very steerable. And so a lot of that steering, you can just put it in the prompt, right? Like, go from point A to point B and the model like, will go from point A to point B. So a lot of, if you have harnesses, that are like designed to kind of do that kind of like steering, you can delete that part. Like that part we actually frequently encourage where you can delete part of those harnesses. I think various people have said things along those lines. And that's, I think what people oftentimes mean when they're like, either the model will kind of consume some of the scaffolding. And like, in that sense, like for sure, if your scaffolding is telling it to go in a direction that it can just intelligently figure out like that, I think will increasingly continue to be so. But as a result of, of this, what the harness needs to start doing is more allow it to run longer. And So that's where like that execution bit tends to be. I think like it sounds like a maybe somewhat silly point, But I do think it results in a lot of differences because you can go in the direction that you tell it to go. You obviously don't want it to stop at B. You're going to be like, OK, now go from B to C and then go to F and then go to Z and then come back to me on A. You know, something funky like that. In order to be able to do a lot of those things, the kinds of harnesses that you do are less the steering harness. And it's more like these kind of strategy harnesses that Caitlin's mentioning, which allows you to operate at a slightly higher level of thinking, which matches, I think, a lot of the intelligence gains that we're starting to see with the model. Do you think task-specific harnesses make sense or vertical-specific or task-specific harnesses? I think people have different opinions on this. Our opinion is yes. I don't think there's a general harness. I think there are some capabilities that are obviously very general and they tend to be very useful. Coding is a capability that is very useful because you can use it across so many things. And software has just eaten so much of what is capable. So our ability to write software is therefore useful. I think when you think about very, very specific. Types of domains that we're going to require, like a couple of pieces of the harness to be sort of like customized. One of that I do think is how you choose to kind of like handle sort of like errors between when you do something and you hand something off to the model. So in like domains where you require like an extreme level of verification, that logic of how you handle that, like, again, I think it sounds small, but like, I totally understand why some people feel like they really want to own the harness because tweaking that last bit will give you a ton of juice. And especially domains like legal and finance, where there's a lot of consequences, um, to, you're not getting it perfectly correct. Like it's really going to matter. And that's going to be the difference between your product and someone else's product being the thing that the user ultimately uses. Um, and then there are other domains for which, like, I would say, uh, it's not going to matter as much because you're able to compress it into like a general model capability. So the tweaks that I guess, like, you know, where we feel like the domain specificity is really going to matter is the specific, like verification logic between the model. And your execution. And then, um, I think it's going to be about like some of these kind of like higher order strategies on how well, um, you're able to actually like allocate your token budget. Um, I think the context bit is actually a little like overdone. Like, yes, you're going to like throw in context and like, that's, uh, but any harness can actually handle a lot of context. And so that's just more like you have the data. And if you have the data, then obviously you're, you're uniquely qualified to do something useful. Yeah. And I think when people say harnesses, they often mean a lot of different things. And I think this is why in part, there's so many different opinions on this. Like you can think of a harness is literally just like a loop. Um, that's like, okay, cool. Like user model, user model tool, you know, like that sort of thing. Um, then you could think of the harness as also all of the tools that are packaged up with the harness. Right. And, and there's just like a lot of different definitions of these things. And I think the stuff that can be pretty generic and like less interesting to own and, and deal with was kind of saying earlier is like. Getting your prompt caching rights, right? Like maybe that is not the world's most interesting thing, choosing to clear out old tool calls from the context window and, and things like that. Right. Or like maybe a little bit less interesting and you like go a layer higher into some of the stuff Angela's talking about, and then you get into like, okay, yeah, these are things that I might want to own and control. And so it's interesting with cloud managed agents, like the thing that we built today, we call it higher order, but it's not really like that high order in the sense that you can. Yeah. Like choose to define all of the tools that you want to bring in as custom tools with the harness. Right. And like, we give you a lot of knobs to control. You can define skills, you can do your system prompts, you can do a whole bunch of different things, MCP servers and things like this. And I think where, you know, we want to get to is a point where you can literally just tell an agent, here's the outcome I want, and here's the budget that I want to spend, like ready, set, go. And you may be like, don't think about any of those things underneath. And so I think there's just a few different layers of this, right? That for certain things, like you might. You might want to sit at a different layer of what you actually go and control. And you can probably get better outcomes within some of those layers by doing a little bit more optimization work. Very cool. One of the things I'm curious about, and one that I love about infrastructure and platform teams is that you get to see what the most advanced users in the world are using and learn from them. I'm curious, what are some things that you're seeing and learning from the people building on your platform? There's some people that have been doing some really funky ways of like handling context. We are. We're doing a lot of self exploring this a lot. That's actually like one of the reasons why TAG is like such a great product is like there's a lot of really awesome like context kind of engineering that that's happening. We've seen some teams be really clever about like how they do that, and they are able to kind of think through like, okay, if I have all these contexts in a bunch of different places, how can I proactively go reach out to them? How can I try to generate enough like permissions across each of them and then feed that all into like an agent? And it's interesting that like, I guess like this is kind of the level of innovation that we have. Like we're actually like very excited by it doesn't express itself as like a completely different product form factor, but what it actually does express itself as is like maximally useful to users, and we've been seeing this more and more with like in actually like internal use cases, instead of like external ones, so like companies who are becoming more AI native, basically, they're the ones we're seeing increasingly more and more innovation out of and so, you know, we've had like customers try to do this for their like they've built their own like custom SDLC kind of setup in very, very innovative ways. We've had ones who do that for like in their entire back office, and just like the kind of nuances of how they like stream in context, I think it's been like actually really interesting in terms of like how they've been putting together the pieces, so that's been like one category that's been like really, really like fascinating. Another category that's been like really interesting has actually been with companies that are dealing with like really old school software, and so there's a lot of like healthcare companies that we kind of engage with, and, you know, like they're like the systems I'm working with, they don't even have APIs, like that's, that's, you know, that's kind of interesting. And so, you know, how can they use computer use and things like this to be able to start to kind of automate and create more connectivity with our systems, and that area of innovation I think has been really exciting it's been really interesting to see people try all sorts of crazy stuff from like taking a laptop and trying to like run a bunch of things on it to auto generate a bunch of things that then their agents can go and use, and this has actually been probably like an area of, I think a lot of innovation coming from a lot of our customers that we want to find ways to like support better and see like, okay, maybe this is going to work. Maybe there are like how can we make this easier for you, how can we help you with some standardization, how can we get it so that you know, like you can just have a spec and then Claude can then respect it, and so it's much easier for you to organically connect a lot of these things, but yeah maybe the general theme I would just give you is like, interestingly, a lot of the innovation that's most exciting out there right now has been this kind of like context and connectivity layer, which has been really fascinating. Yeah, like a good one in that we were working with a customer who they built some agents on. Claude managed agents, they also have some agents that they built on other models and other platforms, and they've kind of optimized each of these agents to be good at the things that they want, they want these agents to all be able to work well together, and they kind of were like, wow, Galaxy Brain, like what if I expose an MCP server on top of this agent so that I can then go and like have this other agent call a tool on that agent, right, and have these things just be more modular and be able to work together, and we were like, yeah, totally, and we sat down with them and worked through it, and it worked perfectly, and it was pretty cool. And so we're seeing a lot of, again, that connectivity layer that I think is one of the cooler areas where people are innovating, but outside of that, one thing that has been cool is just seeing the shift in, I guess, like industry trends of where we're seeing a lot of our usage come from, like we talked a lot about coding, like coding as a category, like, of course, absolutely exploded, and there's so much going on there, and we're starting to see some of these emerging trends, like more recently, we're starting to see manufacturing really pick up as just a category where people are like, oh, I'm going to do this, I'm going to do that. People are building with AI, and like one of our PMs, like, getting on a flight to Detroit to go, like, figure out with these customers, like, what they need and what's going on, and so I think we're going to start to see a lot more just kind of like outside of the box of what people think about today sort of use cases, which we're really excited about. It seems like there's now, there was a, we went through a token maxing moment of history, and now there's like the token rationalization moment of history. What are your thoughts on that, and like, what should companies be doing, and then how does the platform team think about enabling that? Yeah, I mean, it makes sense. It makes sense from the high you start to rationalize. I really like that framing, and I think there's like a couple things that are like top of mind for us on this front. I think like, again, it makes sense, and as these models get more and more capable, you're going to hit like levels of intelligence maxing that are like there that then you want to do the next kind of dimension, and the next dimension after intelligence will either be cost or it will be speed, and you just kind of, you know, go through that across all possible tasks. So, I think that's kind of what we're going to see happening in the future, and I think that's kind of what we're going to see happening in the future as well. So, I think that's kind of what we're going to see happening in the future. And as we kind of see that like happen, you know, something that's like really top of mind for us that we kind of try to spend some time with users on is like, what you don't want to do is like stop AI usage, right? Like, that's kind of the wrong move, and we do actually see some of our customers do that. So, oftentimes, the way that AI spend has erupted inside their company has been through some kind of like shadow IT. You know, like their employees just like want to use it. They find a way. They end up procuring it themselves, and before you know it, like half your org has like found some way to install cloud code. And in that world, it is kind of hard to manage because these things are, again, like they're very token hungry, ultimately. And so, what we try to kind of encourage our customers is like, you don't want to like stop the innovation. Like, if you are getting returns on top of this, you are shipping faster than ever before, you can like run more operationally like efficient, then those are gains. And so, the area that we actually try to encourage people is like, if there is a way for you to kind of construct, again, like a strategy that allows you to kind of like, you know, allows you to design an architecture that says like, given a task, assesses level of complexity. I mean, I'm effectively describing a router, but like there are ways to do this that are like, I think, a bit better now. And so, like this task comes in and has a certain level of complexity. level of complexity for that level of complexity like you can define some rules but for the most part right if it's like a hard task you should probably route that to like a big super smart model and if it's not a hard task you can route that to like cheaper models um designing that thing has a little bit of like there's a lot of technical complexity in that but it's like very very doable and we actually like encourage people to try those kinds of things i think ultimately i think within the quad space it will like make sense it's actually one of the strategies we imagine like designing because the way that we're kind of thinking a lot of these things is like it almost feels like every month there's a new era of something um and if we just take a step back like okay and it seems to be like really fast and so what are the different ways that are recomposable so we can redesign very quickly for any new whatever the cool thing is that month kind of like bit um and so this is like in that category of things where we feel like we can actually just like recompose a lot of our primitives and then design it i think the bit that we do feel really strongly about on the model routing front is like we are designing our platform for quad and we want to make sure that claude is great at like solving all these things so we'll like restrict to that space um rather than you know i don't think we're that interested in saying like okay and then you know you should route to a different model or whatever makes sense yeah and well some of that too is just like i think we have a strong belief that harnesses and and just like the agentic layer should be tuned to the model family that you use it with and so i think there was a period where people were kind of like yeah cool i can like build a harness and build an agent and then just like plug in a different model underneath and then just like plug in a different model underneath and they were excited about routers from that perspective and i think we started to see um like vercel just did this with harness agent for example like some of these players in the space like come up a layer of abstraction and say actually like plug in the whole harness and the whole agent that's tied to a model family which makes a lot of sense and so what we could provide is a little bit better smarter like how do you mix and match the right models within the model family underneath that thing if that makes sense but yeah on the general question of token maxing costs and these sorts of things i think we're just kind of going through what feels like a normal natural cycle for companies and figuring out how to make the best use of this technology and run their businesses really well and really effectively and um it's interesting like before working at anthropic as a stripe and we were kind of in the very reasonable era of like we paid a lot of attention to our aws bill and so you know if someone were to have built some background job and they like didn't quite configure it correctly and this thing's like burning through like cpu or whatever it is right like at any given moment and causing a big increase in spend that's not actually worth it right like we have put in place the guard rails do you find that and then go ask that engineer very nicely to please turn off their background job that's not like within the bounds of what they should be spending for the thing they're trying to accomplish i think those are the things with ai that people are going to start to go and figure out and i think to angela's point the thing that gets dangerous is when you're kind of just like here's a cap and you're stuck within your cap like ready set go but i do think that encouraging innovation encouraging people to you know create really excellent outcomes with this stuff and then coming in from the side and looking and saying like okay well there are a few different ways we probably could have accomplished that outcome right and one is like you take opus and you run it all night and you do something crazy and another is maybe to get a little bit smarter with the strategies that you put together in order to create that same outcome within a lower cost and i think that's the like next layer of thinking that everyone's going to start to do very cool is there anything that you guys are excited about building over the next few months that you can share a hint at what might come next uh yeah i mean i know we said this word like 20 million times i apologize but like we really are trying to build ways for you to compose strategies um and so uh that is an area that that we're like trying to move into that kind of like yeah uh coordination layer of the abstraction um and we want to start at this front because the types of problems that we see people building they are at a layer where it's like in order to get the most return on this you have to be a little clever about like what is the nature of the problem that you're solving so to give you something like concrete like when you try to solve for like let's say you want to build an agent that's like trying to um do bug hunting and you could just send one off to go and do that and it's going to give you a certain double turn a level of return of possibility um and then people kind of get stuck at that and they're like okay my next options are i can like make a bigger i can just like swap the model for a different project or i can just like make a bigger i can just like swap the model for a different i probably bigger model um or i could like let it run like longer and that's pretty much like the only two like levers that you have to like try to make this like bug hunting agent for a lot of experimentation when we do these kinds of things there's like actually the thing like those two those two things are still true but you actually have like a third lever and tends to actually do a lot more than you think it does which is that actually if you were to like best of end the thing it would like give you a lot more returns but like just to be just saying those words are fine and there's plenty of papers and people have published it to actually build that thing and put it into production so you can actually test it on users and see the results for yourself that's like really really freaking hard and you end up building all these like custom harnesses so on and so forth or like you know all that stuff um but we're seeing like this is where the alpha is and it's hard and so like in the same very simple philosophy that we talked about at the beginning like if it's like gives you the return that you want and it's hard we're gonna go try to just make it easy for you so then you can use it to then run the experiments you actually need to run it reminds me of when people are talking about agent swarms a year ago it's some version of that yeah in a whole year yeah oh my god i know we're finally there yes um yeah no i think that that's like that's a type of strategy exactly in the same way that you have like you know one big one that separates a bunch that's another type of strategy and i think people have thought about this maybe the in the way of like human organization i guess it could be similar but if you take it to kind of its end state it's actually more just like the token has a job and i think it's this job piece that we're we're really indexed on and um we see a lot of returns too and that's the thing that we want to spend time with users and the rest of the ecosystem on on like how can we just make that easier for folks to then experiment like we can give you like five jobs off the top of our head and we'll probably like that's what we have internally um and if we give this out to the rest of the ecosystem it's probably gonna be like a hundred thousand two hundred thousand who knows what other combinations that people could put together yeah we want to be able to keep doing this hill climbing on like how do you get the most value the most intelligence per dollar and just put that power in people's hands but around the edges of that we have these personas that have kind of just like things they have to work through in order to be able to like really deploy a i either within their companies or within their products and um that's like the sort of enterprise ready security and compliance controls and things like this but really even just like making the platform more modular in the right ways like being able to plug in different pieces of the solutions that we're building like i want to use memory for this thing over here right or whatever else it is and having a truly excellent developer experience around that because we spend a lot of time with enterprises who are like okay i have this like walled garden i need to figure out exactly how i can plug these solutions in and so we're we've got a part of our team that's innovating on things like strategies and jobs and trying to help you maximize intelligence and they're like that's really cool but i can't actually use any of that for xyz reasons so i think solving those problems is really really important to us but then the other persona is you know the like weekend developer who's like i want to go and build something useful for myself right and they're often doing that on top of our platform and on top of many other just pieces of developer platforms that they're building and then they're like hey i want to go and build in the community and i think for some of those folks there's more that we can do to be provide solutions that are maybe more open or more hackable or whatever it might be for those folks to kind of just like go wild with what we can offer them and have this really excellent developer experience and so i think there's a lot of stuff that maybe i would put in the category of table stakes that i'm really excited about because i think those are the things that then unlock getting people to say okay yes this thing works for me and now i can plug in on some of the stuff that you guys are doing that's really innovative and hill climey to get more intelligence and save costs and things like that wonderful caitlyn angela i feel i mean you were building one of the most important developer platforms in the world and talking to two of you over time i just feel really optimistic that that platform is in very thoughtful hands that care about the ecosystem so thank you for taking the time today to share what you're up to and we look forward to what's ahead thank you guys thank you so much for joining us today and we'll see you next time on the next episode of the show