transcribe

How Anthropic ships the #1 LLM in the World — with Katelyn Lesse and Angela Jiang

Latent Space · 1h 46m · transcribed 24d ago
More from Latent Space Business
𝕏 Share ▶ YouTube 📥 PDF 🤖 .md

Section Insights

# 0:00

Introduction to Anthropic's IPO

What is the significance of Anthropic's IPO?

Anthropic is launching an IPO with a valuation of $2 trillion, showcasing its rapid growth and efficiency in the AI sector. The company has raised over $100 billion while maintaining a low burn rate, indicating strong financial health.

  • Anthropic's IPO is a major event in the tech industry.
  • The company has demonstrated exceptional efficiency and growth.
  • Understanding their financials can provide insights into successful business practices.
# 15:13

Product and Engineering Integration

How does Anthropic ensure effective product and engineering collaboration?

Anthropic fosters a collaborative environment where engineers are product-minded and product managers are technically skilled, allowing for a comprehensive approach to product development and user experience.

  • Interdisciplinary teams enhance product development.
  • Technical understanding among product managers improves decision-making.
  • Collaboration between product and engineering is crucial for success.
# 30:27

Model Launch Process

What steps are involved in launching a model at Anthropic?

The model launch process includes customer feedback, safety testing, internal evaluations, and an early access program for select customers to ensure quality and performance.

  • Customer feedback is integral to model development.
  • Safety testing is a critical component of the launch process.
  • Internal evaluations help catch issues early.
# 45:40

Harness Layer and Hill Climbing Strategies

What strategies does Anthropic use to enhance their AI models?

Anthropic employs a simple harness layer for AI models, allowing for hill climbing strategies that optimize performance. This includes innovative approaches like the 'dreaming' system that enhances model capabilities.

  • A simple harness layer facilitates easier integration.
  • Hill climbing strategies improve model performance.
  • Innovative techniques like 'dreaming' showcase advanced AI development.
# 60:54

Cloud Computing and API Management

How does Anthropic manage its cloud computing resources?

Anthropic utilizes multiple cloud providers to run its operations, experimenting with different compute shapes to optimize performance and scalability across various workloads.

  • Diverse cloud strategies enhance operational flexibility.
  • Experimentation with compute shapes is essential for optimization.
  • Managing resources effectively is key to scaling operations.
# 76:08

User Experience and Routing Logic

What challenges does Anthropic face in user experience design?

Anthropic encounters difficulties in creating effective routing logic for tasks due to the complexity and variability of user needs, which complicates the user experience.

  • Routing logic is a complex challenge in user experience design.
  • Understanding user tasks is crucial for effective routing.
  • Continuous improvement is needed to enhance user interactions.
# 91:21

Communication and Productivity Challenges

What are the communication challenges faced by team members?

Team members often find themselves overwhelmed by communication demands, which can detract from their ability to produce meaningful work and focus on critical tasks.

  • Effective communication can become a full-time job.
  • Balancing communication and productivity is a common struggle.
  • Strategies are needed to manage communication overload.

Transcript

0:00 Hi, today we're la trying something new. We're launching coverage of Anthropic for the IPO. They just filed their S1 as of today and so we're releasing a series of podcasts leading up to the IPO which is expected to be in two weeks for $2 trillion and it's one of the fastest growing companies of all time with a reported lifetime cash raise of hundreds of over 100 billion but a lifetime burn of less than $10 billion. So there are a lot of efficiency stories to dive into there and I think that's something that we want to cover how Anthropic is simultaneously shipping the strongest models in the world while also doing it very very efficiently and building an incredible business. So, I've pulled out, you know, a lot of you know, if you've been listening to the podcast that I have a former life as a financial analyst, and I pulled out some statements from the S1, which I thought would be interesting to give context to today's podcast. And we're just trying this as a new thing because I feel like some of you want that personal relationship with us talking directly to camera rather than talking to our guests, which we've done for 4 years. So the first thing I want to highlight is that Enthropic is an extraordinarily efficient company by human count and that's maybe obvious because it's an AI company. So obviously they're using AI very well. but I think the degree to which they have changed as a company over the past one year is not well understood. So the trillion 12 month revenue per employee is now 6.6 million as compared to 1 year ago it was 1.4 million. So they've grown almost five times the revenue per per employee and I think that's something that we need to dive into more because I think any business owner any engineer you want to increase your revenue by per employee not just to increase profitability but also to increase the amount you can pay your people.

1:57 this is obviously tracked by significant increase in revenue per dollar of compute. It's notable that basically in Q2 of 2025 Enthopic was basically losing half a dollar for every dollar of revenue and now it's making $2 for every $1 in re in cost. And I think that's an interesting anal analogy of like like how enormously huge this inflection in anthropics revenues and business outlook has been over the past one year like this year was extremely critical for Anthropic to execute well and it has done that and I think we're basically going to drive deeper into this and tell that story as much as we can from the podcast external point of view.

2:40 and the one consequence of this entire increase is that Anthropic has just reported its first profitable quarter like not adjusted profit which is profit after if we take out all the things that cost us money. No, this is generally accepted accounting principles gap profit of 19%. And that is enormous again completely flipping from one year ago. more than flipping like a one year ago it was losing 129% of every revenue dollar that came in. So the primary attribution I think that explains this extraordinary efficiency as you know Claude loves loops, Boris loves loops, Dario loves loops and there's two loops going on in Enthropic. The first is the improvement loop. Basically, there is the cycle of you have cloud. Cloud leads to better models. Better models lead to more use cases. More use cases generate more feedback and that leads to a better cloud. And then there's also the investment loop. So revenue from expanding adoption leads to higher growth. Higher growth leads to more investment and more investment leads to more capabilities that leads to a better cloud. So these two loops basically spin together and form an infinite loop that is driving the increase in efficiency until the end of time according to the atropic one. So I think that is our transition from the overall efficiency story to how they execute it. And today we're going to focus a lot on the cloud platform because that is primarily one of the three things that they call the diffusion of cloud in the enthropic S1. So they call this cloud platform or comprehensive agentic development environment. They provide customers with direct access to the primitives to build, deploy, scale their own applications that leverage cloud's capabilities within their own products and workflows. I think one thing that comes up a lot in the discussion in this podcast is the concept of ad fooding where cloud is built with the same cloud platform that is available to you.

4:44 So something that's also interesting in the cloud platform net was disclosed is over 50% of their customers with $100,000 or more revenue on a training fund basis use cloud platform and so that is an increase and an adoption and emergence of entropic not only as a model lab but as also a hyper scaler and a cloud platform which I think maybe is in the name inherent in a cloud platform and a cloud platform but is going from theory to actual practice and this is something that we're focusing on in the podcast. The other thing that I also really try to emphasize which I talked about before is cloud code, cloud co-work, they all use the same primitives that cloud platform exposes. So I think that's really interesting. Ultimately it looks like Enthropic is really positioning their IPO to talk about going from chatbots to co-pilots to virtual collaborators. They use this term instead of agents. Maybe it's more friendly, but it's a lot of the same things that you look for from agents from longunning autonomous work to judgment, selfcorrection and iteration and tool access. So owning a goal and working alongside of you instead of working instead of one app or task. So that's ultimately the context I want to provide for this today's podcast. This was recorded when Opus 5.5 was launched and I would say overwhelmingly among all the high taste testers that we talked to, Opus 5.5 is the best model in the world right now and Enthropic is even just sitting on Fable 5.5 and probably will release it in the next 2 weeks. I don't they have insider information but it makes a lot of sense for the IPO. So let's look forward to that and learn a little bit more about how they build Opus 55.

6:26 >> Yeah. So maybe a distinction that I would make is in a lot of the incidents that people are hearing about and reading about these are incidents that are happening to models not just like everybody's models right that are in training where the way that you're running these models is you like put them in a box and you say like solve impossible task I'm going to stress you out ready set go right and you like can only do what you can do within your environment and the agent is basically incentivized to try to get out of his box and go solve the problem when people are running production workloads on our API or on anybody else's API, you're running an environment where like there are safeguards that are running that are like not necessarily running in training where like the whole point is to actually train the model, right? But in production workloads, first of all, you have those online safeguards just really great. Second of all, you have more of this architecture and infrastructure around what's happening. Like the agent isn't just in a box trying to get out, right? Like the harness is over here, the hands are over there and it's just like not even a problem that you would have to contemplate.

7:30 All right, we're here in the studio the day after Opus 5.5 with Caitlyn and Angela. Welcome. >> Thanks for having us. >> congrats on launching the top model in the world right now. >> I would say depends depends who you ask. >> Yeah, >> depends who you ask. what is the main takeaway personally for you guys? You know, you have you have your official blog posts. The the pricing cuts are really cool. What do you take away when you launch a new model like this?

7:57 >> We're super proud of this one. the team has put in a ton of different work to just go make this one happen and I think we've like really heard the feedback on Opus 5's writing is like kind of convoluted. We really try to clean that up and I'm really glad to see that like it seems to be resonating with people. Internally when we like tried out the model, we felt the same way. So, it's just really great to get that validation. to your point around the pricing guts, there was a lot there and I think increasingly people are looking for good intelligence per dollar and so making sure we get the per dollar part right has been really important. There's some stuff on the edges that aren't really about like you know maybe stuff that we haven't talked about in the blog post which is that we did do a lot of work on trying to make our API harder to distill from. And so there has been some changes that we have made to go and make that a little bit more concrete. And these are things about you know like how do we do like prefix lock thinking or how you can replay thinking tokens across different types of models. and there's been a lot of like work and effort on our part around making sure that we try to adjust things for very valid use cases for where you might want to go and do this like potentially in your compaction strategies and things like that versus in scenarios where the use case of that is actually from like a bad actor effectively. So there has been a lot of threading the needle around those fronts. And I'm glad to see a lot of that go out as well. in addition to just like shipping a model that's good intelligence for for your dollar and also like just communicating a little bit clearer.

9:19 >> Yeah. specifically you're talking about this paper stealing reasoning traces from proprietary. >> Yes. That paper >> which is as far as right I mean obviously they did like responsible disclosure with you guys. It is super responsible disclosure and we're super thankful for for them coming to us. And >> could we for those who haven't heard about it? This is really cool. You could do it. I mean, it's patched, but like >> like what what was it like? Did it cause a freakout in in in anthropic? Probably wasn't that big a deal. I don't know.

9:44 >> I don't know how much this paper specifically caused a freakout because this is something that we knew was a gap. >> Yeah. So, there there's two separate things. There's the Chinese model distillation. Yeah. And then this was a specific technique that was published that was high-profile. >> Yeah. Exactly. I we we've known for a long time that chain of thought extraction is one of the most powerful ways that you can distill models. And actually something like how do we preserve thinking blocks across turns and make that something that's more required is something that we've explored back for a while. And what we where we were at was we always have this really really hard trade-off that we have to make between user experience like user experience changes that are maybe painful for users of the API versus protection against distillation.

10:33 And so how do we kind of walk that line and say we're preventing distillation? And maybe just to take a step back, the reason we don't want distillation is because the entire point of why anthropic exists is because we want AI to create positive outcomes in the world safely. And we run a lot of safeguards classifiers on the tokens that we're producing in order to make sure that they're safe. If someone distills our models and they run those models without safeguards classifiers, there could be bad outcomes in the world. And that's something that we don't want to have happen. So we don't want people to distill the model specifically for the sake of just like using them for malicious reasons or for bad reasons.

11:10 And so it's always an interesting trade-off of like for all the people who are using the models for good, right? Like we don't want to make them have a harder time getting the intelligence out of the models, but we have to make some trade-offs in order to prevent that distillation. And so we had been working for a while on how do we prevent that chain of thought extraction? And like what do we do about preserving thinking blocks in a way that wouldn't be too painful for people? And we kind of think about user experience hits in like two layers. Like one is just like you have to make an integration change and it's annoying but you could still accomplish all the same things that you otherwise would have been able to accomplish. It's just a little bit annoying. And then two is like actually you can't accomplish the same things that you could have accomplished previously. And that's the one that we're like really really really trying to not have happen. And so where we landed with the last couple models is a few incremental changes to have like enforce these preserved thinking blocks across turns and now like starting to be more about like across you know like if you're using multiple accounts and things like this, right? Like how do we make sure that we're ensuring that you aren't able to take advantage of this chain of thought extraction with the models. And so we shipped a couple additional features to help with that.

12:21 We worked actually with a lot of open- source harness maintainers. We reached out to them. We talked to them. We were like, "You're going to have to make these upgrades within your harnesses. We want to make sure you have a good time." As well as obviously our big customers like who are building harnesses on top of the API. And for some of them, a really good example is they have compaction strategies that would have been broken by the need to preserve these thinking blocks. And so we shipped a new compaction feature within the API to replace what they had otherwise been doing manually, but still works with preserve thinking. So it's just an example of like we're walking this line, but we didn't just like kind of yolo out like >> now you have to preserve these thinking blocks in this exact way because we would have broken a lot of people, but we were able to take the time and work with customers and open source harness maintainers and give them what they needed to be able to make that upgrade.

13:09 >> While we're on the topic of it, anything on the other side of distillation? So you know the other half >> yeah no we we have seen that it is harder to distill like through the measures that we are able to to take a look at it has been significantly harder because this is and you know credit to the the researchers here they they did disclose it very responsibly and so closing it down was was great and they did publish the results very publicly and I know it it did kind of trend quite a bit on Twitter so many people could could use it but yes we have seen it that actually from a the areas that we are able to measure it does seem to have reduce the effect the negative effects that we don't want.

13:45 And yeah, the bit I would just add to what Kaitlin just said is I think at least I see a lot on Twitter or X or whatever you want to call it. it's a commercialization problem or something like that. You know, if you can constill a model and you can take this then it's you can run it for cheap and and so on so forth. While true, it's actually not something we really care about very much. We care much much more about this from like a safety point of view u more than anything else. And so that's why we we tend to think about it from that angle more than just like commercially.

14:11 Realistically, if you distill from us, we actually pay us. So, commercially, we like make the money. so it's not really that kind of an impact. it's just more on like making sure that our models like we want to make we want to make sure cloud is like good and cloud could be derived and if it ends up negative, that would be unfortunate. >> Just generally also on 55 because you guys are just fresh off this. One thing that's really fun to establish the dynamic between you two because you also do a lot of appearances together is you're running you're head of products, you're head of engineering.

14:39 How does this play between the the two of you especially for a model launch like you just take an example? So for model launches, so our team works together very closely like between product and and edge. On my side, a lot more of it is about like what is the balance of trade that we need to make between like launching something that has the right like intelligence bar, but also the cost preservation. like a lot of like our updated cash costs and things like that are indications of us being like we want to like encourage you to take integration changes that are beneficial for actually everybody and just like pass the savings on. but a lot of these kinds of decisions around that and then how do we balance some pieces around our safety motion as well as making sure that it's like an awesome model that people can can take advantage of. And so those kinds of traits around like I would say maybe the qualities and surrounding components around how we launch the model are more on product and then from an integration experience standpoint a lot of that is from like the engineering team directly. So we work obviously if you're like talking about the experience of an API that's like very very very tightly integrated and so it's actually been really awesome. We have a lot of engineers who actually are deeply product minded and we actually like love that and similarly on my side there's a lot of like product managers who are much more technical and we want this like blended kind of interdisiplinarian type of people because then they can kind of analyze it from all the different angles to try to figure out how how to do that best. But I tend to lean a little bit more on like commercial impact versus I think I'd actually frame it as more like the engineers are going to care much more about the integration experience. so they almost take more of a UX angle to it. where the UX is obviously more about the API and the developer tools.

16:17 >> Yeah, it's fun to be a product engineer who works on developer products and platform. So I would echo that. I think we have a lot of engineers who love thinking about the product, who love thinking about the user experience, who love thinking about the developer experience. I think it's a dynamic that we have between ourselves too where I have a lot of opinions and am annoying with our product team on how we think about these things and our product team is also really technical and they can get in the weeds of the decisions that we're making for scale or for whatever it might be. which is a fun dynamic that our team has.

16:48 >> Yeah. Something Kayla and I have worked together for a long time. and >> Stripe and >> at Stripe and then I guess we did not work together at OpenAI but just separate labs and then I came over but I think some one interesting property of both of us has been Caitlyn frequently actually gets mistaken for a product manager and I frequently get mistaken for like someone in engineering even though like those are not actually our job functions and so I think that pairing tends to like help out a lot with just making decisions that are consistent across both sides.

17:18 So I I think I come across a lot of companies with a similar like product leader, engineering leader setup as software engineering gets solved. Maybe those two roles merge. >> I kind of think so. Yeah, I think everyone tends to leave. >> If you guys are, you know, separate still, then we we're not there yet because >> we're definitely not there yet. >> So So like why, right? Like what's left? >> I think that like software engineering getting solved is I would I don't know if I would ever use language quite that strong. I think there's the way that I tend to think about these things like ambitions will continue to elevate right and maybe a good example like a lot of what our team is spending time on right now is of course obviously all the things that we have to do to launch our model safely is actually the most important thing that we're doing because of all the work that we have to do on security with agents with offline safeguards and online safeguards all these things that are happening but the other half of what we're doing is trying to scale and part of that is because when I joined Anthropic a little over a year ago. We had the messages API. It was a Python monolith. We were running it in a, you know, single GCP region and everything was fine and none of my friends and family like knew what cloud was when I was going to take this job, right? And now we're in an extremely different place. And so the metrics are really wild in terms of how much volume we've seen and have had to support on the API. CPU is really constrained, which has been a really interesting one for us. and so we've done a lot of work on how do we scale these systems and that takes a lot of obviously just like distributed systems expertise and certain language and frameworks expertise that the models have. But when it comes to operating and evolving a system at scale like this, we're not quite we're not nearly in a place where it's like good luck cla have fun and just go and kind of make all the changes you need to make to the system, roll them out safely and operate this thing at scale. there's still just a lot of work for humans to have to do that I imagine will continue for a while.

19:09 >> I'm curious how that's changed. So like a while ago, you know, when Fable first came out, we had Glass Swing and there was a whole delay and change in how models start to get released. We saw this for most Frontier models. there's safety testing. What's the status of things now? How do you guys see it? How do you determine like one thing is there's a new Sonnet and Haiku also coming. I assume those will just come out. But for something like Opus 55 or a new fable, what's the what's the current status?

19:38 >> Yeah. So, I would say this starts with what our kind of policy decisions need to be on safeguards and on safety. and that's both offline safety and online safety. And so there's been a lot talked about lately around data retention and what we're doing there in order to, you know, release these models safely. And the reason for that is because you have, you know, situations where there are many many accounts across like a whole giant network of people who are choosing to spin up accounts and use the models in various ways and there's no way that in an online way as tokens are flowing through the system, we would be able to kind of catch that there's something malicious happening with the models or distillation or whatever might be happening. And so we've started to have to have data retention policies so that we could do automated review and human review whatever it needs to be to make sure that good things are happening with the models and with each model that we're releasing like that's one example of a policy decision decision that needs to happen on like what will the policy be for this specific model. and so Opus 55 that launched yesterday, for example, does not have those data retention requirements that Fable has, right? But that's a decision that we have to make each time we're launching one of these models. And if it is going to have those policies, we're going to have to do the work to make sure that those things are enforced. Similarly with programs we have like we have cyber verification programs and now newly our life science verification program which says you know like you have a difference in how the online safeguards are working for the model that you're using making sure all those programs are in place is another one and so it's just kind of a flavor of the type of work that we've done as part of each model launch that these are everything that I'm saying right now are not things that we used to have to think about when we were launching these models. and now it's it's the majority of the work is like what are we doing to prevent distillation, the online safeguards, the offline safeguards, the policies. A really great example is we built a system to make sure that authorization for being allowed to use a model or being allowed to use one of these like programs that give you maybe like relaxed safeguards. That authorization threads all the way down through our system in a way that we can really trust. You know, it's not like, oh, you got access to mythos and so we throw you an API key and we flip a feature flag and call it a day. we have a really robust system on how we're doing off and making sure that if you're supposed to be using that model like only you are using that model in the way that you're meant to be using it. So there's a lot of complex things that are starting to happen around model launches that again we just never used to think about.

22:07 >> Yeah. And it's it's scaling up with capability. Like as our capabilities get more and more advanced and they start to spike, you know, in specific areas, that's where we need to pay like extra attention. And so a lot of that evaluation comes just from like those very particular capabilities that we might either see as like offense dominant or defense dominant and therefore might take different strategies for all of that. And as we bake that all the way through to eventually the model launch, there will be components kind of like Caitlyn mentioned where we kind of don't exactly know how people might use those capabilities. There are some more obvious ones like between coding, right?

22:39 Like great, go make awesome products, go ship more things. it can be really awesome for you. And then other areas like bio and cyber, it's like it could be dual use and there could be negative effects, but obviously of course you could be a really valid cyber security researcher. You are trying to find vulnerabilities. You are trying to be a good actor. Similarly with bio, you might be researching and stuff like that. And so a lot of these programs like the one that you you have up here are to basically provide access to that dual use. You do have to specify your use case and things like that. but we do want to enable the community to be able to take advantage of these capabilities and see what amazing things that they can do with it as well.

23:13 >> Well, we'll put up the links and I maybe we'll dive into them later. There's also one for bio. Also, I just think at a high level, you know, it's it's really important that you guys actually think about this stuff. People forget like Fable was rolled back and there's all this distillation and people are like, " zero data retention is not a thing on Fable. Crazy." But you have to remember like, you know, it got pulled back. there's distillation attacks like it's good you're overthinking and doing it in the right way while releasing it, right?

23:40 >> Yeah. And a lot of that is like building the right framework. just so again kind of talking about the edge side a bit building the right framework in our system to be able to do that. So I talked a little bit about this like this idea of like authorization and trust grants that we've built throughout our system. Now >> never say never, right? Not not as not as precedent. but also it's like a very common thing in platform engineering that you like you have one incident and then you like overprepare for the incident and the incident never happens again.

24:06 >> Yeah. >> Like you know now you have the button. >> Well it's true and it's funny you say that because it was a like with everything going on we then had this line item in our you know the work that our team was doing that was we're going to put this system in place that makes it so that it could be a single button to pull back for everybody. But and so it's funny cuz it's like do we justify that we're doing this work cuz we don't we hope that something like that never happens again. But I think in this case it's really just a lading up of those same primitives that we wanted to put in place everywhere to help us manage these verification programs and access to models like Mythos and otherwise to just say like just sit that same thing below like everybody's model access so that in case we ever needed to we had the right controls in place.

24:48 >> Yeah. And decisions like this have actually proven to be like we'll see about this one in particular but examples like this have been consistently the way that we've had to actually transform the way we develop our road map because you know in traditional product management I guess you can be like okay like these are the set of things I hypothesize to happen they will have like a certain sequence a certain ordering but you are picking bets in a way that are much more concrete versus like you know the deployment of fable for example I don't think any one of us would have guessed that that would have been like a valid use case that would have by the government and the way we just like had to go do it. But clearly the probability is non zero. And so from this form of thinking it's become deeply probabistic actually from like a product management standpoint of like so should we prioritize this? What are the chances of it ever happening again? When we look at things like that we're like okay if we are to imagine the most crazy set of possibilities we probably actually have very little certainty as to where things will go. And so we actually just kind of need to like hedge and build a portfolio of bets. And so more often than not, we will take hedging scenarios of like, okay, we don't think it would happen again, but in the event that it does, we would actually want that hedge or have the ability to be able to do that very well. And so we will prioritize things like that. And then we have increasingly found that more often than not by taking that strategy of product development most of the time, we actually find ourselves being like we actually do use the thing.

26:10 >> Is there another example that's a separate one just so I can understand? For example, this this access program. This access program is a really good one. This it's internally it's it has a bunch of granting and all these kinds of things. We developed it specifically for reasons about like being able to actually give programs like this out to customers like very very specific high level what the access program specifically is. >> Sure. So if you want dual use if you want so for let's let's take a model. So you take a model call it like opus and you want to be able to use advanced cyber capabilities on on opus for research or for whatever you want to go do like your your defensive user you can apply to this program to be able to with your use case and if approved what we'll do is actually diminish the safeguards on your version of the model so that you can then go ahead and try to take advantage of those like cyber activities for for your use case. Now obviously that requires like per use case understanding. It requires scoping down to a particular user because you wouldn't do that generally. You'd have to like apply and even things like this like this kind of program we designed a lot of the primitives that Caitlyn was talking about to be able to handle things like this. Now it was surprising to us or maybe like you know in the portfolio approach we found that we were actually able to take this and make it ex we're like when we're designing it we're like what kind of should it be?

27:26 How generic should it be? Should it not be too generic? to just be overly focused on making this verification, you know, style portal plus granting of a very specific capabilities of the model. And we tended to opt for like more genericism because we were like, we don't know like maybe we can use this for other things, maybe not. And then would ended up being massively useful for things like you know access to the model at large for managing any of our trusted access programs for handling deployments of models because we were actually very very generic about how we handled every single primitive.

27:57 From a normal product standpoint I would normally probably be like that probably doesn't make a ton of sense. We should focus on the use cases that make sense. But here increasingly because we choose the more generic approach we find ourselves reaching for that solution more often than not and it pays like increasing dividends for that reason. >> It's something that you needed to have anyway and you just have to forcing function to have it on a technical basis. What so I am I'm from the AWS world right IMC and then people like who get really intense about this talk about Zanzibar and all these all these other technical architectures.

28:28 >> I'm not familiar with the word token grants or or like trust grants. Sorry. >> Trust grants. trust grants. Is there a difference between normal offse and and what trust grants are? >> I mean, not really. It's it is it's a it's a form of authorization >> I am but anthropics. >> Yeah, kind of. I think so really we have there's like authorization of the form of like okay you're you made a request to an API that like under the hood is going to access some data and we're making sure it's like your data that you're accessing, right? Like really really vanilla authorization.

28:58 This is just like we put a data model in place that's like a very clean like a trust grant means like you have been given access to some specific model or you've been given access to some specific program or you know like there's a bunch of different permutations of this we actually find ourselves reaching for it all of the time. another good one was when we first rolled out some of this preserved thinking in or for the for Fable 5.1, we kind of grandfathered in some people and gave a bit of a you know just like a grace yeah grace period to go and make the integration changes and as part of grandfathering in we said okay we have to like track who is like an existing customer who needs the extra time right and then we did a trust grant and so then we're able to say for anything. We're just running this service that is kind of on the hot path of our requests to make sure that you know, we just like flow through and and check whether you have the grant for the thing that you're trying to do. which is it's really not any different than like vanilla authorization really, but like we just had to spin up a system that was specific to our system and like where we needed to be able to insert these checks.

30:07 >> Yeah. I mean I think these are all like the engineering things that people kind of take for granted don't really think about. What is another example I guess of the platform stuff that had to happen you know maybe serving cloud code maybe serving you know obviously I talk a lot with cognition but other customers just in terms of a model launch right like we'll talk more about the the the the safety work that is that's being happened I just want to sort of go at a high level because it's fresh off your memory like what goes into a model launch >> it's become a bit of a a machine these days minus the safety stuff which I think is the more complicated part. But outside of those pieces, there is a lot of getting feedback from our customers.

30:49 So, you know, we make the model, there's a lot of safety testing. there's also evaluation of where we think it needs to be. We make the required trade-offs and decisions as necessary. And then we have to go through testing. we'll cut various versions of the model. We'll evaluate it. We'll do a lot of internal ant fooding as well. And that actually always really helps like we catch like really early things like this is, you know, maybe not the best. And we obviously use cloud a lot for our work internally. So we're able to actually see early signals around stuff and it helps us detect like you know which which variants might be better than others. And then when we feel really confident with like a certain set of of variants we will cut a version for our for our customers. sometimes that will go through our first party products like through cloud code or co-work or things like that. in other cases it will go through our API customers.

31:33 and we'll engage in a kind of like a early access program effectively with those customers. they'll need to make changes into their harness. And we've engaged with a lot of customers like like Cognition, like like Herser, like these folks. And we have a bit of a process on how we handle that. so that we all kind of get they always get the feedback that we we need. Does it perform well in your evals? Do you like it? What don't you like? Some things are are vibe and we like to hear those things too. and something we just like straight up evals like did it do well on the things that you care about?

31:59 >> And we take that all together and once we all feel good about like all those different pieces, we launch the model. The state of model feedback is feels very unstructured still. >> Basically, it's always a slack channel between companies of like, hey, this thing seems weird and then people are like, okay, I'll fix it, I guess. Give me an ID or something. >> Yeah, it's very I mean, it's it's the nature of like a product like non-deterministic, right? Like, but I think to your point, the only customers really that are part of our early access programs are customers that have really robust emails. Like I do think a lot of this is vibes based and I think a lot of the conversations tend to be kind of like vibes based and and on the fly and part of that is because we're like racing right it's like we want to minimize as much as possible the window between we have a version of the model that we've cut for testing and we give everyone access to that model and so it is just like this really tight window but the customers we tend to do it with are the ones who like we know they're going to go like kick off their whole eval suite and be able to come back to us with like really actionable feedback as quickly as possible alongside the vibes the vibes based feedback. So, of course there's like definitely like processy things that we could do to make these things better over time, but I mean you'd be surprised. I mean, you probably wouldn't be surprised, but I think some people would be surprised about how few, you know, like products that exist in the world that are agentic that like don't have good evals to be able to help test these models.

33:25 >> We had Boris on the pod two years ago saying we don't have you also clock code. I mean that's changed but that's that's changed but you know like yeah a lot of things like you know your emails are your users and you don't have time to formalize them or you don't have the experience or whatever and that's fine at some point when you get serious you you'll have emails. >> Yeah totally. >> I think the good thing is you guys do a lot of amp fooding as you say. So it's commonly said that you find a lot of this testing it yourself before it comes out right.

33:50 >> Yeah. Yeah. The API customers in particular are very useful because they'll put cloud into a different harness. and we want cloud to be very very general. so its ability to work in other harnesses is is quite important to us. And so that style of feedback tends to be exceptionally useful for us because it's it's novel from what we would have gotten from an >> what kind of feedback helps. Is it like regressions? We have regressions here.

34:12 We notice good attributes here. >> the good stuff is always it's always very validating. I think we're very frequently not surprised, but we like to look to be validated on some of those things that we might hypothesize. Honestly, the most useful feedback is negative. like you know, it didn't do well at this, didn't do well at that. We love that feedback and then we're like, great, how do we fix it? >> Yeah. And it tends to be some of these things that are like it's really hard because not everyone actually wants like Claude to land at the exact same spot on every spectrum. And and maybe a good example is like, you know, laziness versus proactivity and taking action.

34:46 And so there's sometimes when like we have a model and and people are like like just finish my task like stop being lazy like do better and other times when it's like hey we were like just kind of feeling this out and planning and then you like went and wrote a bunch of code or you went and like took a whole bunch of action that I wasn't ready for. And getting that exactly right is literally impossible because everybody actually wants something different in reality.

35:08 But I do think we've had situations where we've cut an early version of the model. We found that we saw too much laziness, right? and like we like put it back in the oven for a bit, right? And and tried to train that back out. And so those are the sorts of things that we may not have caught if all we're doing is internally ant fooding within our products and within our API. It's way way more important for us to get that out there in the API and get all of our other customers running with it and let us know what we need to change.

35:36 >> Yeah, it's a core question. And I think it's probably the if I if I were in your shoes like one of the hardest things about PMing for a model which is let's call it alignment versus personalization. There's a default personality a default behavior that you want for all consumers and then you want to be able to respond very quickly to someone's cloud MD saying no no no like please be more proactive than default. and then like so as to my knowledge you know and I was involved in Frontier Code we were involved in the fable launch which put Frontier Code on the map and now Opus 55 we have it back on on on the the model benchmark that is a very big part of Frontier Code right the reason that the model curve looks weird for Frontier Code is because it penalizes too much activity or too much files. which is good like there was a whole design purpose of French code but like I could easily just be like in my cloud MD just say like don't do that and then it won't do it >> and >> so like am I penalizing cloud opus 55 unfairly because my benchmark doesn't have that personalization element which is subjective so I don't know what the question is but like how do you deal with like personalization right like it's it like clearly a model can do so many different things and it's so depend everyone has their own cloud MD. how do you eval?

36:56 >> Yeah, we don't do a great job of it. There's like the there's seriously it's it's really hard. It's super hard and they're they're competing. It's horrible. >> I thought I thought there's the cloud constitution. I think >> that's old. >> There is a constitution, >> but I'll I'll let you guys answer. The constitution is helpful but but for things like this on how it personalizes to instructions which are different and preferences which are very very different across these things is very hard for us to do. We generally try to solve this by having more parameters that then allow us to tweak it per customer base and if we don't control your customer base and you're an API customer then we try to give you recommendations and then you try to do that tweaking. So there are things like you know around doesn't exact it's not exactly the same level like personalization to the cloud you know various cloudmds or now agents MDs or whatever but we do try to give things around the layer of like level of effort like how much effort you should put in like what are the like the level like maybe the size of the model that you might actually like try to care about things like that but it's I think it's it's not quite there for what we would actually need for like that level of personalization so it's a very hard problem and right now a lot of our way to solve that is beyond the parameter like the giving multiple parameters or something is try to exhibit conflicting taste honestly across like all of the feedback that we get and try to try to make like a judgment call on some of these things. I think over time they actually and as you scale to more customers and more users that's like not a very scalable way to go do something. and we will need to develop ways for cloud to kind of like take in your personalization. and maybe that's like a signal you can provide or something you could tune on or things like that. but I think we'll have to like take a route that's much more oriented towards that direction. but for now, yeah, no, we we actually just try to make judgment calls on on a lot of the stuff, but it's it's pretty tough.

38:46 >> It is what it is. >> A small a small note there. I guess the default effort reasoning changed. It's now medium. This is one of those things that probably affects the average customer that doesn't use this toggle. >> Yeah, it's like a cloud code setting, right? >> It's a cloud code setting. They defaulted to medium. >> Yeah, they just >> And this and this thing varies. This thing does like this is a this is a perfect example of a parameter that we use to kind of like personalize. I I would say this maybe a little too aggressive of a term, but we kind of like customize maybe for different subsegments. So like the default setting will adjust for whether you're a free customer or proumer customer, cloud code versus codework versus enterprise like things like that versus API and stuff like that.

39:23 knowing that you can obviously always adjust it but those are kind of like light ways where we try to give that. One thing that we are hesitant to do is we don't want people to feel like they can't control their customization of quad. that we could take a heavier hand on these things for example, but we want to give users the ability to experience the intelligence levels of quad as they kind of see fit, especially if you want to go towards like the higher end or you want to experiment with maybe sometimes in in the lower end if that actually is like faster for your use case, which is a hard product trade-off, I think. and so we we tend to lean towards gentle defaults, but give you options to to adjust, which I think works okayish for now, but I imagine us, you know, like learning how to do that better over time for customers. We're not like super super happy with any of this yet, but we know as we launch a model, like you asked like what does it take to launch a model? One of the big things obviously that we have to do is like, okay, Claude like got good at a thing and like sometimes that thing is something we should expose as a parameter on the API to let you control. But I think as this has evolved over time, we've ended up with like this funny mishmash of like there's effort, there's budgets, there's all these things that you can set on the API. And it's like how could anyone like possibly figure out what is the right combination of things for any given task for what you should go and set. And it's something that this is us just very much like figuring it out as we go and figuring it out with customers and figuring out like which of those parameters do we deprecate over time.

40:48 Which of those parameters do we just like default better? Which of those parameters should be like a one to a 100 scale versus a low medium high scale, right? Like because actually we've trained Claude to get really good at understanding like a whole spectrum of options on some of those sorts of things. But like do we expose the like entirety of those millions and billions of permutations of options like you wouldn't really get very far and that's one of the things actually that is part of the value prop with something like cloud manage agent which is like still programmatic access to cloud and an API but you get a harness out of the box where we do every time we're launching the model a lot of the work to go figure out like what are the new parameters what are the breaking changes how do we get the best out of claude within our harness so that for the people who are using it you just kind of get that out of the box. You don't have to think about it.

41:36 >> Just for people who are drawn to that and which there's a significant and growing population particularly we actually did a whole CMA workshop at EIE which I thought was really well done. Is there a separate feed for people to subscribe to like updates on CMA >> feed like >> Twitter feed newsletter? I don't know. No, I think actually our our Claude Devs channel, we are Yeah, we're we're pretty loud about it. because it is like an interesting option for people.

42:03 >> Yeah, I just want to give people like if that's your if that's your way of consuming cloud, that's the this is the path. >> >> I think it's also pretty underrated. for those that aren't consuming cloud this way, >> what is cloud managed agents? Why should people use it? >> Oh yeah, we should probably do a do a little intro. I don't know. That's somebody's house. Yeah, little two two sentence thing. I think a lot of people glanced over it when it came out, right?

42:26 Everyone was in this phase of I need to do harness engineering. I need to control this and like you hear all that and now it's like do you need to do all that or do you just use managed agents and you have a lot of info you can skip over setting up but give give the quick three. >> Yeah, it it depends on your use case but so cloud managed agents is our API today. We have the messages API which is essentially raw token access. Then we have cloud manage agent which is a suite of APIs but it lets you define an agent start a session with that agent. and it's essentially just kind of a higher order abstraction that lets you skip setting up all the infrastructure setting up your harness and doing a lot of that type of work. It's a much more out of the box integration for people who want to programmatically run agents.

43:11 >> Does CMA share infrastructure with cloud tag? Because the sequencing of it seemed very like oh like that's the cloud tag. A lot of it. a lot of it. So, one of the big things that we do is as the platform team, we run our APIs. We also kind of run all of our foundational product infrastructure and product services. So, like really good example is like our team runs our sandboxing fleet that backs both cloud manage agents as well as products like cloud tag and otherwise. But at the actual harness layer for those two products, like there's just differences in what we might want to do within the harness so that they don't they don't actually share a harness. but they share a lot of the infrastructure that powers the execution and powers the APIs.

43:56 >> I think that's that's really people should use this more. I I think everyone basically had copycat clones of manage agents after you guys launched it which yeah, you know, imitation is a sincere form of flattery. Since we're on this topic, we'll briefly mention all the memory stuff that has been going on. I feel like it was a big part of Anthropic's work in the first half of the year. Has it stalled out? you know, is is it still still ongoing? Like what's what's the emphasis here now?

44:21 >> Managed agents specifically. >> Dreaming. >> Oh, it is a big part of what we're doing. I think maybe the way to think about it is we launched managed agents as a platform for people who like didn't want to do all these things themselves, right? Or just wanted to like offload like I'm getting the best out of Claude because our team is literally sitting here like evaling all these things and making sure that the harness is going to be really powerful. Memory and dreaming is all about just like how do you make sure your agent can continuously improve over time and all of that is still an important focus for our team. But what I would actually say is to the point of what we talked about earlier as launching models has become harder and harder from a safety perspective. I think most of our team's energy is going less into like here's a fun feature to like hill climb on this agent or whatever and much more into how do we bring safety into all these things because the most important thing that we can do is get the power of the model out there and get it out there safely. And so I would say a lot of our energy is take all these same concepts and give you an agent system that's going to be really powerful but also that's going to be really safe. And so that's where we're putting our energy. I think compared to maybe earlier this year, we have slowed down on like skills, dreaming, memory, like these kind of like moment in time.

45:37 >> Skills. >> No, no, no. We love skills. >> we we are making we are making updates. I'm not saying that we're not doing anything, but we we love skills as well. But yes, so I think we've slowed down a little bit comparatively for some of the other efforts. But we are very bullish on people kind of doing some level of hill climbing at the harness layer. to you know some of the previous conversation here we do a lot of this ourselves but the harness that we provide is very simple in a way.

46:03 It's it's intentionally simple. we don't want to be actually overly opinionated. want to make sure the best practices get merged in and there's some kind of undifferiated pieces of the hardest agentic loop that yeah are hard to string together and also like you can kind of just boilerplate do it. Now the interesting part on top of that though is like once you get get that base layer there are these like hill climbing strategies that we construct and like dreaming is actually one of them. So dreaming under the hood is a multi- aent system that we hill climbed on top of CMA and it's actually a CMA on top of itself basically.

46:32 >> CMA on top of itself. >> It's it like spins up another Yeah. the way Germany works is that we spin up another manage agent that then can expect the previous manage agent and then write memories to that manage agent. So it's manage agents all the way down and this is a bit of thing by design because we envisioned that you could probably put together a lot of these modular components for something interesting and dreaming is just like an example one of the more interesting things that we were going after. but we kind of have been looking at this and being like there's actually a ton of other stuff you can do. You can do like best of n as a type of like multi- aent strategy. you can do a verifier agent, that kind of like goal thing or outcome thing. there's a bunch of other stuff in there and we've seen people do some pretty funky crazy stuff like there's been a harness that like shares like crazy memory across everything and they spin up like tons of parallel agents and we're like we should actually just probably enable you to do that in the same way that we did we built Dreaming that's like manage agents all the way down. There's a update that we'll make relatively soon where we're updating the underlying primitive.

47:29 we'll expose it to allow users to kind of like construct harness strategies maybe or however you want to call this >> like multi- aent strategies >> multi-agent strategies that allow you to kind of build your own version of this and we'll give you like you know templates of like this is how we started with dreaming maybe there's like an update to this that you would want to make as a developer and you would find some more value on top of that >> yeah I think that's a really good framing it's less that we're slowing down on this sort of stuff and more saying like we've got the primitives in place we can continue to let people just like take and run with those things while giving them the tools to say here's some like cool multi- aent strategies and like things that we've put into into cloud manage agent to make it really powerful. Now you can like let Claude do work to take advantage of those primitives and make it even more powerful yourself like create new multi- aent strategies and whatever it might be while a lot of our team's attention turns to okay great like community run with that right and and you do you while we continue to focus on what are all the things that we need to do to make sure that you get access to the models within that system safely. One thing you brought up was you run a lot of evals on this stuff.

48:32 >> Pretty hot topic right now. Any advice, best practices >> for eval specifically? >> Evals on harnesses, agents. >> There's a lot of different types of evals, right? Like not all eval are made equal for different, you know, like situations that you're in and things that you're trying to test for. You obviously have just like static deterministic stuff and then you have LLM as a judge. You have all these different strategies. But I guess I would just say like what we found from most people is like you probably need more rather than less.

49:02 it's just there's not like one perfect like couple sets of emails that you could put together that are going to get you all the answers that you need to make your system better. We found that people end up needing like a relatively large suite of these things and then it's like you can have your agents work with you to evolve your eval suite over time as well. but I think it's just like not underinvesting is maybe like the biggest mistake that we've seen from people on that front. Yeah. And it starts simple. I think some people like go a little crazy and they're like, you know, they're like, look at all the the menu of options that you kind of listen.

49:35 You're like, wow, this is so crazy. Let me try this and that and what's the best one? And like while they do all those things, like the number of emails they actually have are like zero. So, you might as well just like do something simple. It will help. >> yeah, I think in some some part of it people are inexperienced. They're not trained to do this. and they don't know what good looks like. And I think for you guys publishing more examples of that is is really helpful. something I I I do tell people a lot that I'm doing with more fable and astroclass type models is we're treating engineering like research.

50:05 >> And when you treat your engineering like research, you naturally do more evals, you do more labeling, you do more scaling of runs or like prototyping and scaling of runs. And you're not training a model. You are building the harness, the product, whatever it is, but you're approaching it like research. You're defining up front what your goal is, trying to formalize it as an eval, and then trying to identify, okay, why why is it failing? And sometimes your eval is wrong.

50:29 >> Totally. >> Actually, a lot of times your eval is wrong, sometimes your environment is wrong, >> and then sometimes the model's wrong. >> and actually that is like a lot of part what I think AI engineering is becoming, which is doing all this stuff. >> Completely agree. And we'll continue to launch more features within cloud manage agents to give people more tooling to do this sort of stuff out of the box. And you'll probably find from us that you'll get something that's like here's a product that will help you create evals for your manage agents or whatever it might be and it'll feel very much like working with claude in order to do that is like >> that is that is the best way to do it.

51:02 Cloud's actually really good at creating evals to >> evaluations actually because like people like blur blank out when they look at like JSON L's like just >> right but a pretty eval UI where you're like left right left right left right and you're you're sort of like doing what the human graded data people labelers would do anyway >> you can do that yourself just like throw fable at it >> and it'll materialize but also write comments so because it just like outputs all these ratings right it'll give you an eogo give do whatever. But, Claude can just consume that and then work on itself, right? That's the feedback it needs and people just don't know that you can prompt for an email.

51:41 >> Yeah. >> Yeah. I love that you said that. I think it's like a very like AGI pilled way to like do it. because it also allows you to update and edit that system like very systematically. And so, as new models improve, as things change, you can really inspect where your system is and it'll just like evolve, >> tune every part. >> Exactly. >> yeah. So ba basically I think it's it's you know how we talked about how maybe product and engineering are are emerging. It's also there's like application layer engineering and and sort of model research are sort of merging in in those techniques that they're being shared right like >> that's very true >> model people are very very used to doing eval application people know like the only thing you care about is does it fit fit the PRD and like >> yeah it's it's like a whole different >> it's a whole new skill set I think for >> I think you guys put out a pretty cool blog post on this today. It's somewhat different. It's about making the UI a lot faster. But to your point of treating it like research, basically define a goal of we want stuff to load faster and then define and you know question things. What can we do instead of wall clock timing? there's fun quotes in here. I think it's nice to see how the actual researchers or engineers prompted Claude. There was stuff like, you know, we had we had 12 things. We said you have two weeks. I did nine out of 12 of them in like 3 days or something. But fun blog post for people to research, for people to read through.

53:01 >> Yeah, I love it when we share our actual prompts and and like some people are like, "Oh god, they must have crazy unique ways of prompting." And it's just like try harder, Claude. >> Thank you. >> my only feedback is it should link to the workbench, which is no longer a thing, but I used to >> That is a good That's a good idea. Workbench. Okay, good. Everything feedback heard. Love it. Yeah. yeah, but you were going to share more details behind the engineering story or the the rush work that you >> Yeah. So I think I talked a little bit earlier about like scale is a problem for us. scaleafy, right? Like >> Yeah, scale and safety. Those are like the two biggest things we're spending our time on. and I mean it's really interesting because most people are used to talking about scale or just like I don't know computes at the like GPU accelerator layer and much less so at the CPU you know like old school layer and that's it's it's just like as much of a problem today as the accelerator layer which is really interesting. You cannot get enough VMs.

54:03 You cannot get enough sandboxes and just everything being able to spin up, spin up >> with all the resources that you have. You >> really you got a lot of customers too, >> which is crazy. Yeah. And and think about it because we're using CPU across obviously just like running our product services, running the API, running all of our apps. We're using CPU on sandboxing, all the sandboxing that we're doing. And then just like all the things ever like CI, you know, like you'd be surprised how much more code is getting written. Therefore, there's so many more CI runs. Therefore, you need more CPU to handle that. And so, on the whole, and this is not just us, this is everybody that I talked to.

54:38 >> I would add training. Training is probably using there's a different bucket, right? I'm sure they don't coingle that much. Well, they don't coingle. Although like CPU for Anthropic as a whole is is is like a zero sum game, you know, like we get our we negotiate our deals with, you know, the CSPs and we get our CPU and we have to allocate within anthropic how much of that goes to all the things I just mentioned, including like research sandboxing versus product sandboxing and otherwise. And so we really are allocating across absolutely everything.

55:10 And it's just everyone in the industry right now is you and everything. >> Yeah, you used to be able to just like, >> you know, like scale up on demand into CPU capacity if as long as your budget allowed you to, right? And like now it becomes something that you have to capacity plan for in advance, which is, you know, like kind of punching everyone in the face. It's brand new and people are starting to do it. And so dealing with that means a few things like one is obviously just go try to get more CPU.

55:39 Cool. We're doing that as much as we can. But two is we want to be able to at the infrastructure layer run it more efficiently, right? Like figure out how we can make sure that we're running our sandboxes as as efficiently as we can without compromising on things like tenant isolation or properties that we like, you know, care about for security or otherwise. But then at the application layer, how can we how can we run our applications and our APIs more efficiently? The thing that I'm like most excited about, as of last week, we fully rolled out the messages API.

56:10 written in Rust, which is one of those like insane feats of like what you're able to do in the agentic coding era that used to be like we started talking about this like earlier this year. We were like we're going to hit a CPU wall. There's stuff we need to do and and we've done it right like we've gone multi-reion. We've done all these things we need to do >> and we were like we're running this Python monolith and it's like it's like very CPU inefficient. and so what are we going to do to make the system more efficient?

56:39 >> Yeah. So, we chose Rust, which was a crazy decision at the time because we had a team of people like on paper it's obvious, but our our team was like, "We don't have a single Yeah. We don't have a single Rust developer in the room. Who cares? Just >> Exactly. Literally." And and not only that, but yes, Claude is going to write the code. The humans like design the system, right? So, like the humans are very involved in making sure at the end of the day, it's just like a it's a distributed systems architecture, right?

57:07 And you both also help those engineers like you know bounce around ideas and learn what they need to learn to design that system. But what's most interesting is the two things that mattered most were the plan to do the thing and then the verification of the thing cuz the actual implementation was like claude writing code. Yeah. And so what we ended up doing was we literally built like an entire fork of the entire API in Rust and then started running shadow traffic through it and verifying that the outputs that we were getting from the Python system and the Rust system all you need.

57:42 >> Yeah, literally load balancing feature flags. I don't know. I never in my career would have had a team say like Yeah, yeah, cool. We're just >> Do you still have the entire people or no? No rest people? well they would probably call themselves rusty people now. >> I mean there are a few big step to run. >> Yeah. Exactly. and along the way we have hired a couple people who have more experience rust but yeah but it it still is just like you never would have signed up for that. It would have taken years and years and years. Like you wouldn't do it all in one shot. You would have carved out pieces of the system and say like migrate this, migrate that, migrate that. Easily a >> multi-year but you would never like kind of one in one swoop, right? like port the whole thing over and then just like slowly turn it on. But that is what we ended up doing. and it worked. And so, not only do we actually save a lot of CPU, but we our latency has seen a nice improvement, which is pretty cool, too. and you know, it's just it's it's a crazy era we live in because you just never could have done that sort of thing previously.

58:42 >> order of magnitude of savings on the on the CPU side. >> ju just for people considering this. >> Yeah. Yeah. I'm Okay. Order of magnitude. That's really interesting. So ballpark. Yeah. >> Yeah. Ballpark. I guess I would say like we've s somewhere like 40 to 50% something like really crazy. >> Yeah. >> And then latency. I think we saw somewhere between like 10 and 20% improvements on like time to first token specifically. So a lot of just really cool improvements across >> it's higher on like longer running workloads, but so it'll it'll roll out soon but it'll get faster.

59:17 >> Do you fight the the urge? You know, I've been involved in some major rewrites. There's always like >> what if we add this new thing that didn't exist before in the rewrite since we're rewriting anyway, right? >> But then like that adds scope. >> Yeah. >> So, do you just like avoid that? Is it a pure >> rewrite? We did. It was a pure It was maybe the thing that I would call it is like a port. What we did was we we did exactly that. We like resisted the urge on all these things then and because what the team already had to keep up with was little like swap team that we put together to go and do this was doing this while the whole rest of our team was like building features into the API, right? And they did all the like static analysis stuff. They would yell at you because you built a feature over here and you didn't consider Rust over there, right? And like they dealt with all of that, but they resisted the urge to add features themselves or like make the system different. Now their next goal is to go and do some sort of rearchitecture type work including stuff that I think will be more userf facing like we're starting to roll out some things that are like you know what if we were able to not have you have to like pass back and forth the entire like conversation state right and if you didn't have to do that on the messages API because you were open to like you know a storage of that state for some period of time right then like especially for long conversations where the context really builds up like you get a lot of really great latency and efficiency wins there too. Like these are the sorts of things that the team that was doing that port was like ooh like what if we do this right >> then you're catching it yeah I have that >> so we have prompt caching yeah but you still have to like pass back the state of the conversation >> okay >> very very niche small subsets but I guess this is the level >> no this is this is this is important yeah there's a lot of savings that can be done but it also turns them into a cloud >> yeah from from type of from number of users point of view it's small but if you look at the actual token volume on those those types of workloads it's like going I'm very like like what Cloudflare did with durable objects. I I feel like every cloud provider should clone. Do do you know what I mean?

61:15 >> Yeah. >> Like right is isn't that the right shape for a messages API that needs to continuation. >> Yeah. I mean it is really interesting because I think what we're we are experimenting with various like what is the right shape of like how we should run our compute in order to power all these sorts of things. but it's also interesting because we can't necessarily rely on like because we get our compute across we run on all three clouds. we're running all over the place. Like we don't necessarily have like one shape of here's exactly like the compute the types of machines that we know we're going to run on and the way that some certain compute works that we can like rely on across the board if that makes sense other than like the most vanilla versions of these things. But I think these things are all going to I don't know continue to innovate and evolve as time goes on and so we'll be able to take more advantage of those things.

62:00 >> Yeah. I'll just mention if people want open source cloud durable objects Rivet is the open source equipment. there are 50 people listening that will kill me if I don't ask this question. You want CPU, they have CPU to sell. Who do I sell to? Who do I email? >> and what do you what you know and like what is what is a good help them help you, right? Like what what does good look like? >> Well, I guess like email me.

62:26 >> Are you sure? I don't know. >> I'm going to get a lot of emails. But like you're you're looking like minimum fleet size sock two with obviously enterprise like all give me all the >> privacy >> guarantees for what it's worth like so we have a really awesome team that secures our accelerator compute that is now spending a lot more time with us on CPU and like where and how we can procure it to make sure that we can just continue to run our systems at the scale that we need to and so it's not actually like my job thankfully is not to go and and run around and try to procure compute But we do have teams that are doing that which is really great and really important. But obviously like there's a quality bar that matters to us. There's like a scale bar that matters to us. We're not going to like go and integrate and run on certain machines if like we can't get enough of it. And so all the properties that you might expect of a system at this sort of scale is all what matters to us.

63:20 >> Then related to the compute problem is the sandboxing problem. people have trouble >> containing agents in sandboxes. They keep breaking out. what's going on there? What's the state of the art? >> Yeah. >> So, state of the breakout recently. >> Yeah. It's interesting. One of the things that we did with cloud manage agents specifically is the way that we architected it. We put out this blog post at the time of launching where we talked about we have the brain separate from the hands. And what that means is like the harness runs on a durable server really ours right. And then wow me nice.

63:52 and the hands are it's like a execution environment like a sandbox or some sort of container, right? The part of the reason why we did this was for like latency and reliability and these sorts of things, right? Like if the harness is just running on a durable server and it's only spawning a sandbox or a container to execute when it needs it, that means we can get you tokens back really quickly on your initial request. It means that your sandbox can die, but like your whole agent doesn't die because the harness is durable and over here and the you know the agent storing state separately also. And there was a whole product development journey that we went on to get there because our first iteration of an API for agents was just like throw cloud code in a sandbox and like shove an API on top. And the reason why we didn't launch that as our like durable scalable solution is everything that I just said it was like you got to boot a sandbox and boot cloud code before you can even get a token back, right? The sandbox dies and you lose your whole agent. And so reliability wasn't where we wanted it to be. So we architected this way mostly for reliability and latency. But the interesting thing there's actually a the product manager who worked on this from the very beginning was like the most important property of this architecture is security and everyone's like yes yes yes but latency and reliability and like now now they're vindicated.

65:03 >> I literally I apologized to this person yesterday. I was like I'm now like telling everybody who I meet about what you've been saying for months that nobody was was as excited about as as this person was. One of the more important properties of this architecture is you have credentials for any any work that the agent needs to execute, right? Like if you're going to go talk to an MCP server or if you're going to go like use a CLI or call some API, whatever you might want to do, right? And like you need to authenticate those things. You need to store those credentials somewhere so that the agent can use them. And the way that we architected this was we have a totally separate vault where those credentials are getting stored. And as once the agent decides like I'm going to go and call out to one of these services, the agent only ever sees like a placeholder, right? And like on egress we have a proxy that goes and like pulls the right credential out and injects it and lets that out. And so what's interesting about that is like the agent is never like in the same place where the credentials are, right? Because in the old world of like just boot the agent in a box and like let it run, you had to send credentials in there and then you're like doing some sort of like how do we like scrub this and that and make sure that like the agent can't take that credential and go do something that it shouldn't be doing. It's just like literally a like literal infrastructure wall that says the agents like can't access those credentials and can't do anything bad with them. So that was one thing that was really great. The other nice thing is like on that sandboxing infrastructure, we can make sure that we have really great egress controls. So we have like domain allow lists and things like that or you just like totally shut off network access so that you can't say okay agent wrote untrusted code that code executes in sandbox and that code can like reach out to the internet right like now it only can reach out to where you say it can reach out to. So there's a lot of really great properties around all of this within the architecture and within the way that you can configure your sandboxes that make it so that you end up like secure by default. One of the the things that's starting to happen is as we're talking to customers who are like I want to run agents either for you know a product for my customers or internally but I'm like you know hearing about incidents where agents are breaking out of sandboxes and bad things are happening. How do I think about these things? I think the two most important things are architecture so that it's like literally impossible for an agent to do something that isn't okay and the configuration that you have on those sandboxes. And so one of the really really nice things about cloud manage agents is you just like get that out of the box and you get something out of the box that like as we learn more and we continue to evolve the properties of those systems, you kind of get that for free cuz I think say all the words that just came out of my mouth like brain and hands and credentials injection and egress and all these sorts of things are just like if you go back like nine months like no one would be saying these words, right? like these are all like relatively new problems that we're solving and so we want our customers to be able to take advantage of the solutions to those problems as we're even learning about them and solving them ourselves within our infrastructure.

68:01 >> Yeah. And internally we're just upgrading everything to be basically >> that >> secure by default. Yes. >> we also unlock something that we cover in pod which is the cloud brain local hands. >> Mhm. >> Which is projects. >> Yeah. >> Is that is that the rough shape of what's going on? >> Yep. That seems right. Yeah, I I I feel it's weird because obviously you're famous or cloud code is famous for being the super unsafe dangerously allow permissions thing on on your machine, but now you're like finally evolving to where it probably should have started in the first place.

68:34 Basically, I think like all these sandbox leaks, right? Are they a fundamental issue with our our understanding of sandboxing or container tech or are we just bad at this, right? Are we just like not disabling like not doing the allow list, right? like it sounds like we're just not doing the allow list. >> Yeah. So maybe a distinction that I would make is in a lot of the incidents that people are hearing about and reading about these are incidents that are happening to models not just like everybody's models, right, that are in training where the way that you're running these models is you like put them in a box and you say like solve impossible task. I'm going to stress you out. Ready, set, go, right? And you like can only do what you can do within your environment. and the agent is basically incentivized to try to get out of his box and go solve the problem. When people are running production workloads on our API or on anybody else's API, you're running an environment where like there are safeguards that are running that are like not necessarily running in training where like the whole point is to actually train the model, right? But in production workloads, first of all, you have those online safeguards which is really great. Second of all, you have more of this architecture and infrastructure around what's happening.

69:41 like the agent isn't just in a box trying to get out, right? Like the harness is over here, the hands are over there, and it's just like not even a problem that you would have to contemplate. And so I think that some of this is just like people having the right understanding that what's happening, some of these incidents that are happening in model training and otherwise are just things that like wouldn't happen in production workloads where a lot of work has been done to put the right guard rails in place so that those things like never really could happen. The second thing I would say is just like everybody's figuring all of this out like relatively newly because you know longunning agents is a relatively nent thing that everybody is building and trying to deal with and so everyone's figuring out some of these things on the fly and just racing to put the right you know like controls in place and you know some of that is just happening as we go. So I would say it's not, you know, we're people are bad at this, right? I think it's just more it's a nent field. People are figuring it out. And I think when we talk about things like pacing the frontier, the way that we think about it is really specifically we're doing all the work that we're talking about right here for all of our agents internally and making sure that all these things are accessible to all of our customers so that like by default the right guard rails are just in place so that you don't end up having agents doing things that you don't want them to be doing.

70:55 >> Fair enough. well cuz you mentioned pacing. We got to go there. We also talked about the last last time. It is superficially contradictory to advocate for pacing and then also release a new frontier model 11 days later. To me it's just it just means that it just passed your safety checks. Right. >> Yeah. And that yeah everything we talked about earlier on like how we launched the models it's like we are continuing to evolve more and more and more safety properties in place again across these like I kind of am starting to think about this in these three dimensions. It's like the actual like architecture and infrastructure security then it's the online safeguards that are running when a model is doing its work and then it's the offline safeguards classification that's happening on data at rest. So across all those three dimensions, we're putting all the right work in place to make sure that we feel really good that we can put a model out there and it's going to be safe. And really, that's fundamentally what we mean. And so for Opus 55, it's an excellent model. It's also really, really great on all the dimensions that we care about across those three things.

71:58 And therefore, we feel good about releasing that model. So we went for what we thought we were hoping is the best possible user experience within this while we continue to hill climb on making those false positives better. But it's obviously like it's still a frustrating experience for people when you're trying to work with a model and then you fall back to a different model. And so it's just something >> I think people also understand it in the safety sense like you want more false positives, right? Like >> it's a safety issue. We clearly see the whole faces incident and you're still giving access.

72:28 >> Yeah. To to me this is like a a a close cousin of the general model routing problem of do you want a smart router or dumb router? Does that make sense? like because as far as it can tell the the the anthropic fallback router or detection thing is a separate model that's online >> it's it once it hits a classifier there's just logic to where right like so it is not the full fable right you're not you're not you're not you're not running full fable at it and that that's going to cause classification issues because it's not it's clearly not as smart as fable like clearly so then there's a question of like well then like when I have a classification issue that's that's like an unjustified fall back like you never you never need a fallback. I'm just doing my bio homework but I mentioned bio one time and then it come falling back. so like there's a question then this is very similar to the routing problem because like >> you're routing models and like how can this the a dumb model route to a smarter model if it doesn't even recognize this that's that's a smart model problem.

73:25 >> Mhm. >> how do we solve this? >> It's a hard problem. I think I think in some super alignment sense models are good at classifying stuff but not answering them right. not the smartest model can tell this is a dangerous query even if it can't make any impact on that. So >> I think the super simplifying thing to say would be like basically you have the smarter model figure it out over the one that it needs to detect.

73:50 >> I think it's lower as cost there there's trade-offs there. >> There's trade-offs. I'm not saying it's like the right user experience but it would probably be a slightly more >> effective. Something interesting is you also don't cut off immediately. I've seen cases where it will start answering, start reasoning, and then get hit by a safety filter. So my first example with Fable was throw in the Fable safety guard >> and it started I was like just break down anything interesting in here.

74:15 Starts breaking it down 5 minutes in I think it gets into cyber security and it's like oh we're cutting we're rolling back to Opus. But it did a lot. There's a lot of context and >> I see it. It got to a point where it's all about cyber security safety and then it rolled back and it's like it wasn't rolling back my query it was the combination of reasoning and the whole chain right >> do you have a idea of >> yeah let's brainstorm what better >> I think the user experience and how we resolve that user experience is probably you know a separate question like maybe it's going to use a super smart model to handle it or or whatever but I think that the more appropriate UX that I would imagine for a user is to actually have a more consistent unified experience with Claude where instead of getting you falling back and then you can double fall back, there are like logical points in our tree that that do do that for again like safety reasons and whatever. But I think that UX is just like really convoluted for a user.

75:09 It's like you almost you you're trying to do something and I I would probably take the case of like a good user and you're a good user just trying to sell your buyer homework like assess the cyber security like safety card totally reasonable and you get blocked and you fall back and I think instead it was just to be like you are our model should have gotten or classifiers or however you want to do this would be smart enough to detect that that is a situation that happens and just write down the me the answer for you more concretely while dropping down the nature of the like negative use of that particular capability. So going back to that bio homework scenario while we may have classifiers that have detected that it is possibly B I'll also say like the on the API we went with a spectrum of solutions for this for customers. So first of all like if you've built something on the API and you run into a block like you don't have to like continue the conversation on a fallback. That's what we've done in our apps and we've made that a feature of the API and you can do it like server side within our API. You can choose to like set I want to do the fallbacks, right? And like we'll do that. We also have it within our SDKs on the client side. There's helpers for if you want to like manage fallbacks in various ways or you could choose to like reprompt differently in some way, right? And and continue with the same model. but I do think that there's some in between interesting solutions that we'll continue to experiment with to figure out how we unblock people and and do so safely but with a good user experience.

76:37 >> Yeah. >> And then you brought up the the bit how it's like very similar to routers. I think like I totally agree with that. I think it has a similar UX problem as well. Like with the router you you go through it's like let's say you want to do a cost router, right? For the task complexity that you have. Makes sense. very hard to do. you don't know everything upfront about your task. So you can't like even with perfect you just don't actually have perfect information even if you could actually understand each model perfectly which you don't but even if you did you also don't have perfect information about your task and so there's a lot of error associated with your your routing logic that you would have to create whether no matter how good a classifier you produce and yeah maybe it's like a super big brain model type of problem but regardless it's I think a very difficult one and in each one of those like scenarios if to find a way to like route that properly it's very very convoluted you could expose all that logic to customers like hey you your task was to center a div, so I'm going to route you to something super cheap.

77:26 and like then this other one's like detect vulnerabilities, so I'm going to route you to something like really expensive. a pose all of that. I don't think that's like a great user experience ultimately either. And for that similar class of problem, I think the more idealized UX would be something along the lines of like dynamic like effort or dynamic like understanding of the level of complexity of your task which you might actually evolve over time as you learn more and more information about the task. But in that world, if you're kind of like moving between a lot of different models, it actually becomes very very disjointed. And so like maybe a more unified approach would be something like it's a consistent model but on it's like very very low effort level or something like that. It's actually very very cheap and very very affordable but it can scale itself up very very continuously but you have like a very very consistent persona towards that model and obviously I'm speaking about this in the context of like you know like our family of of models if you try to even do that across other family of models other model providers like the personality the disjointedness like starts becoming very very complicated. I don't know how you solve it in that layer but at least within like our family of stuff like I'm more bullish on things that are just more consistent and those might be ways to solve it more robustly for customers. Yeah, you're you're not responsible for anyone else, but within cloud, yes. Yeah. I mean, this is your your territory.

78:38 >> It's nice to see the way you guys think of these problems, right? Intent in and of itself is a hard problem. Like I feel like the models have gotten better, but sometimes people don't do a good job at classifying what they want or they just slider all the way to one extreme or, you know, the model doesn't really understand. You're asking a simple question and it's like, oh, I have a whole HTML landing page now. I just expected a few line output, you know.

79:02 It's all there's always a a mess around there. >> Yeah. >> I think we we in this conversation where we talked about a lot of safety, we talked about like launching the models like all this kind of stuff, but it's obviously in in pursuit of helping power the workloads for people and like we discussed kind of the earlier part of this conversation we are seeing workloads change quite a bit. I think like in some workloads intelligence does seem to be increasingly saturated which is like a a new situation. and it's it's getting to the place where I think there are some class of tasks that are still very very unsaturated. I actually think there are more than maybe people anticipate, but they're increasingly going into the direction of you get that alpha or that return by doing extremely long running agentic tasks on things that historically you were not really able to brute force, but maybe you can with a lot more intelligence behind it. and those workloads are really really fascinating to us and we see a lot of value in that kind of area both from businesses getting that value from themselves as well as you know like new companies or startups or however you want to frame it who are interested in building kind of like a egentric products on top of it. I think if you look at the class of things today, a lot of it tends to be it's obviously a lot of coding stuff.

80:08 There's obviously a lot of like enterprise innovation acceleration kind of stuff. but they tend to take the shape of automating a very distinct and specific process. And I think in some areas that's actually really starting to work, which is awesome. In some areas it still isn't. So there's still a lot of like room to to kind of evolve and push the frontier for those models. And then there's like this new class of workload like the the bio stuff that we talked about or some of the cyber stuff like that's a it's just a very very complicated set of like I would say hard engineering or hard science problem. and those workloads are increasingly showing up as well for us as like a really interesting space to just deliver value to customers.

80:43 >> You know you you are at one of the few spots in the world where you're discovering all these workloads and we're automating it. It's like >> yeah it's pretty crazy. >> I mean you know that's very inspiring. you guys are having so much impact and and I'm really grateful for that. We're going to go into a few closing questions which I which I thought would be fun to sort of bounce back and forth between the two of you. how do you fight slop on your teams?

81:10 >> so we actually this has been an interesting debate within our team. The the we're no different than anybody else, right? I think plenty of teams are talking about this. and what's interesting is what we're trying to figure out is if you're producing a document, you're producing something that you want other people to consume, code, documents, whatever, right? If like you should use claude to help you, of course, right? But if you use claw to like totally generate a thing, you didn't spend any time on like actually reading it yourself and making sure that it was something of high quality, then you're putting a whole extra burden on the consumer of that document or of that code or whatever to spend a whole bunch of time trying to parse it. And that's just like insane and totally unfair. But what's funny is we, you know, we push back, we push on our team like you can't do that, right? Like if you're producing something, use collage, sure, whatever, but like you have to make sure that it's a high quality thing. You as the human are still responsible for the quality, >> right? You're still responsible for the quality. But then you get into this really funny thing where because of the claudisms even just like silly like I don't know there's like an M dash in the middle of the thing, right? Like people's brains trigger on this like oh no I'm reading something that was written by Claude and not a human and I'm like annoyed because I want to be like reading a thing that was like fully produced by not necessarily fully produced by a human but like that has the quality bar that the human would hold, right? And so then we get into funny situations where maybe actually like the person did spend a lot of time making sure the thing was high quality, but they used Claude to help them, but there's those little hints of Claude and then the reader is like turned off, you know, and like that's like unproductive as well. And so what we have kind of tried to do is like set a bar within our team that's very much like use claw to help you because it would be really silly if you didn't use this hilariously powerful agent to speed you up in your job and in your life or to just like help you produce better things. But it has to like have a certain bar and then for the consumer and the reader if like it really actually is just slop like send it back, right? Like just say no, just send it back. Like you're not going to waste your time on this. but also don't be like too nitpicky about the little clawisms, right? Because like we have to find our right balance here. And so it's just really funny because we're, you know, we're going back and forth on this stuff within our teams and just like so is everybody else in the world right now. we're just not any different.

83:29 >> But but you have free tokens. >> well, sure, but I mean it that doesn't tend to matter quite as much when it comes to >> So you have more than anyone else in the world. >> You probably see a lot you guys use a lot. you see a lot more people doing a lot more. >> Yeah. Yeah. It's totally fair. But it's definitely it's definitely >> heavily discouraged. >> Yeah. >> engineering slow. >> Yeah. I mean it's same thing, right?

83:52 Like but but I do think that where where we've gotten to is a pretty good spot where like you know humans play a large role in making sure like designs of systems are good, right? And like implementation tends to be clawed, right? And like we're in a pretty good spot where for like a lot of the code that gets written like all you really need is just like a quick stamp and you can keep going. And like you don't necessarily have someone like deeply reviewing every single line of the code because you care more about like the overall plan, the overall like design is in good shape less so than like the exact perfect implementation and obviously rely on a whole bunch of verification to make sure the thing that you're going to ship is high quality.

84:30 And so it's actually been like less of a conversation these days on like code quality being slop. In part because cloud's just like gotten better, but in part because we have a lot of the right verification in place to make sure that like you know we're holding a high bar. >> I see. I see. You trust your tests. >> Yeah. >> >> any product PMing slop. You can ship features a lot. You can put stuff out in a day.

84:51 >> So he said this to me recently. Do you remember what he said? >> Th tweeted this. The right way to use model capabilities is not to ship 10x more features into prod. spend more time understanding your users, trying experiments, building whatnot. But basically, you know, you could very easily just keep shipping random SLO, but you you should actually think about it. You should spend more time kicking off that first prompt. I know now today he's like, "Kick off plan mode. We don't need it anymore." But outside of plan mode, you should think about what you're doing, right? It's very easy to put out a lot and you can get products solved.

85:25 >> Yeah. I mean, I I tend to kind of go on this rant about there's a lot of just like fundamentals about how software gets like and products get planned and shipped and otherwise that like doesn't need to change just because agents are like helping speed up certain parts of the process, but there's this inherent like almost laziness is starting to come out from a lot of people where it's like, oh, I don't have to like think about some part of the process at all because the agents are doing it and helping me or whatever. But like those are still like incredibly foundational parts of the process that like should be things that you're spending your time and energy on. And I think that's kind of the spirit of what he's getting at here.

86:02 >> It's just like as a founder or creator, let's call it as well. it just feels like because the cost of experimentation or exploration is so low now that I should be doing more of that. And he's basically saying to not do that to to like use it in service of a a very intentional goal that I start from the start which like obviously I'm coming around to it's just hard. It's like you have this toy that does everything. It's just like throw it at the wall.

86:28 >> Yeah, there is scope too. So like the blog post of today was 2 weeks to make cloud AI faster. There were 12 things. we hit there were 13 things. We hit 12 of the 13 targets in 3 days, right? Well, you could just say okay it's a twoe sprint. we'll do the 13, but instead there's 20 things you push bound. This is not product slop. It's not new products. It's refactoring. But still, you guys do a very good job at outputting a lot, but keeping high bar quality.

86:55 >> Yeah. Nice. >> Okay. Part two of three. this is going to make Angela very uncomfortable. This is Angela Tweet Corner. I will tell >> Nice. I I will I will tell people nonstop to >> I and I I I'm pretty sure you've deleted stuff >> because I'm like there's there's stuff there there's stuff in your deletions that I'm like so >> Yeah, I know. Like really like alter my DNA. >> Oh, I appreciate that. >> What do you refer what do you think about the most? What do you refer people to the most that you want to sort of bring up? And I can I can pull it up for you if you want, but >> I actually I don't think I have a favorite, honestly.

87:32 No, I really Okay, I guess maybe I like the one that you say where it's half doing something is expensive way of not doing it. Maybe that's >> that's very on topic for us today. >> Okay, but I guess you know obviously you're in a different job now and you don't do this anymore. But like I think this is a power tweet. This is like a naval rob you. >> Yeah. >> That do this. Uhhuh. >> And like what mode of what like what framework of mind frame of mind of mind?

88:05 >> That's a good question. Yeah. No, this was a very long time ago. I went through a period of my life where I was like reading constantly actually. I found myself like very bored of the stuff that I was doing and I felt like I was just like not being like intellectually challenged. And so I actually went on this a bit of a bender where I I think I read something like 200 or so books in like a year. and I was just curious about like every I just wanted to like read everything. And I was missing a little bit of like the the kind of like intellectual like I don't know like muscle building you get when you're like in school where they like do like this is a new topic you got to learn. It's like tough. It's like not super fun actually but you are really like stretching yourself. And I felt like after just like working for a couple years, I just like stopped doing that. Like yeah, the job's like interesting. I guess it's like challenging, but it doesn't have like that like intellectual bit to it. So anyway, I went on this bit of a a bender a reading bender. and I like read like 200 books in a year. It was great.

89:01 I had like a really long commute, so it was like it was a good use of my time, very long like hell train ride. But I ended up coming out of that and being like I was just like thinking a lot as a result of that. And at the time it really wasn't to build like a Twitter followower or anything. I was just like tweeting into the like abyss. There was like I have like no followers. These were like tweets for myself and I was like practicing a little bit of like how would I try to compress the idea that I have in as few words as possible. It was kind of like the personal test I had for myself and then I guess people just started liking it and so I just I just kind of just kept going at it and then I got too busy with work and I I stopped doing it. So >> I got to ask after all the reading any book book recommendations, blogs, long articles.

89:45 >> My favorite one still is probably The Black Swan by Nasim Talib. that was like one of those like I was like kind to me at least it was like a bit of a like a life-changing philosophical book where I was like that's a completely different way to look at the world. And >> you know I was thinking of Black Swan when the fable thing happened, right? It's a thing that you didn't know could happen. now that it happens like it's a it permanently changed your framework of >> exactly how things work and the idea is like so simple but I think he did a great job of just really hitting it home and articulating it and how it's like a common property of actually of so much of the world. So I really love that book and that's probably my favorite.

90:22 >> and for listeners if you're bored with that one you do fool by randomness randomness also by Taleb. Did you like fragile? >> I guess so. So the the more famous he got the more intolerable he became. >> but also question for Kaylin. My if you do have one. Do you have a similar like this is a book I recommend to everybody. >> No, that's a good question. I need to think about it. It is funny cuz I do think we have very different styles on this front. Like she's no longer like in fortune cookie tweeting mode. But I do think that like you stop that. But I do think a a big part of how you work and how you work with other people is like philosopher mode sometimes. You know, >> you drop fortune cookies in Slack.

91:01 >> Oh, I I do actually. Not intentionally. I think it's might be somewhere success of succeeding in dropping is like you have to be very good on Slack. >> Yeah. Oh, you guys have to be very good at Slack. >> it is it's a pretty intense place, but I think I'm a little So, I'm kind of psycho about like inbox zero on both email and Slack. It's easier on email these days than Slack. but I like pretty aggressively prune like here are the channels that I'm like actually in and paying attention to versus the ones that are like muted below the line sort of thing. And I'm like always making sure that I'm on top of the ones that I need to be on top of. But it is it's basically it feels like a full-time job.

91:37 Like there are days where I'm like I could cancel all my meetings and write no documents, do no work, right? and literally just sit there like on Slack the entire day and I would have done what felt like an entire day's worth of work just by like engaging on Slack with all the things. It's pretty wild. >> No, but that's horrible. But what >> So that's exactly how I feel. I feel like you do all this, you put in all this effort and yes, like you you met the mark on like responding to people and getting certain things over the line, but you didn't actually produce the output that you wanted to. And like that's like a that's like personally a very hard thing for me to deal with. I try to be like I need to like dedicate time to like actually thinking and actually like trying to produce something in order to feel like I'm like actually >> and ignore and drop stuff, right? You're going to drop stuff.

92:16 >> yes, I have gotten a lot of feedback. I'm a little hard to reach on Slack. >> yeah, pretty thing that happens now is I get a lot of slacks saying, >> "Can you get Angela to respond this?" >> And I'm like I'm like really trying to write it down here. >> Wait, so you guys don't have like a personal claude like assistant something? I don't know how to help you, but there's >> Why has no one no one written in like a personal EA for each of you?

92:42 >> Yeah. Well, so we do have we have a human one also. We also have we have plenty of cloud help in Slack for sure. but I do think actually the the types of Slacks that I'm like when I'm pruning through and getting are often just like our team is like blocked on something because there's some hard decision that needs to happen or whatever it is, right? And it's like it is just like a form of whether it's in Slack or some other way, right? like it's a form of getting the team unblocked, like executing at high quality. That is my job anyway and it like happens to happen a lot in Slack.

93:13 But I do agree that it ends up feeling like what did I even produce when you get through a whole day worth of literally just like going back and forth with people and trying to solve problems. >> You produced the a functioning team that's unblocked. So I will give you a prop for that as a as a former manager. That is Yeah. Yeah. Yeah. You don't feel like you you produce anything but like you produce the team.

93:32 >> Yeah. >> Yeah. speaking of your team, I was gonna go to you next, Caitlin. Deell Corner. >> Oh, nice. >> we are I know you're really hiring De making a call out for for developer relations. you hired Addi Osmani recently. >> Yeah. >> great get Lance, you know, you build up a team. what what do you guys want to hire for? You know, this is this is it to talk about it and I'm happy to trade notes.

93:57 >> Yeah. Well, props to you because I will say when >> on the outsourc recruiting Kaitlin recruiting team >> literally literally >> it's fun >> and it's not it's actually not even just recruiting like I'm going to toot your horn a little bit when so I when I joined Anthropic we you know we're a small team we're like all things considered we're an extremely small team and so we run the platforms the API business and and all of our product infrastructure and we we had like a very nent Devril function within Anthropic that was, you know, like not necessarily within the product and engineering org. And when I joined, we were like, okay, we like need to grow up a little bit and need to figure out how to like engage with the community, engage with the world. And, we need to like really invest in this Devril function. And, we ended up spinning up a Devril team within platform and a Devril team within cloud code in part because it's like two pretty different like developer ecosystems that we're trying to engage with across the API business and agent coding, right? And so, We ended up doing it as like two separate teams but kind of like dotted line to each other and spend a ton of time together. but it was it was something that I was going to be responsible for like Debell which I've spent plenty of time with Deell before at Stripe or otherwise but it was never something that I was responsible for and I was like I have no idea what I'm what I'm doing and you were like I got you like here are the three pillars of Debell like here's how you think about it which is really great across like product content community and then now I can like rattle that off to people and they're like wow you really understand Deborah. I'm like, "No, stop me."

95:27 >> You're like, "I copied that." >> Yeah. That that was not >> It's apparently that post is apparently like the default reading for Google when when they on board new, Deborah. Like really funny. >> Yeah. >> it's it really like this this really helped me because I had no idea what I was doing. but then on top of that, we you know, like I've I don't have a manager for the Devril team within platform right now. And so that's one of the things that I'm hoping to hire and our deval IC's report to me directly in part because I think it's a really really really hard problem right now, but also in part because I find it really fun and I'm having a lot of fun working with the team. But really specifically like what's hard on platform is platform in some sometimes in our like public narrative like our platform business is a really large business but it can kind of get lost in between research and policy and all this work that we're obviously doing that's like our most frontier important work and then our applications like cloud code and co-work and all the things happening over here. when you think about Anthropic and you think about our public narrative, those are some of the things that often come to mind and less so that we're running this like massive developer platform business that's really important and so many people are building on top of. And so a big goal that we have with our Devril team within platform is figuring out not only like the really classic like how do we better engage with like you know product like what people are building and how we get feedback back into the product and these sorts of things but a lot of it is just like finding our voice and finding what our brand needs to be and what our narrative needs to be and like who we even are going to be in the community and not kind of get lost in all of the things that are happening. And so that I think has been interesting because I think the brand that we've started to spin up for our Devril team in part because actually Lance joining our team was you connecting me with Lance but Lance is highly technical and the way that he goes about Devril is very much like teaching right like he writes a lot about memory and managing costs and these sorts of things and he goes really deep. He builds evals. He like has a lot of really technical content that he puts together. And I really like that idea like that idea of our our Devril team being kind of like thought leaders for people within what is a really nent really hard really evolving space.

97:36 >> Educators, thought leader, explainers of things. there's another version of this I really like called the master builder. which is I will build the things with the platform to show you what's possible and then you'll be like I didn't know that was possible with the cloud platform. And then you just go. And this is a thing stolen from Lego. >> Yeah. Because Lego, how do they sell Legos? >> They have master builders. They build things with Legos. And you're like, >> I want to do I want to do that. I want to be like this person. And then they they they do that.

98:03 >> Nice. That's awesome. Yeah. And the CJ, the other person on our team who's really great as well. I think he also does a lot more of that sort of you know, writing cookbooks and like putting out examples and really engaging with the community on X. >> Cookbooks is funny, right? like when APIs launched in 2023, let's call it for LMS, very important. Now, >> not so much. >> I don't know. >> Yeah. Well, it's interesting because you're less in the spot where you'd like copy paste the code and like use it, right? but I do think it's like it it shows the art of the possible for people and just like what even is the use case, right? And like how could you go about accomplishing it? But I hear you that like you know the code itself is maybe less like we for the longest time had this like there's there's an engineer on our team who wrote our cookbook on computer use and it like haunts him to this day because it was like massively complex and like you know kind of a beast of a thing that I think you know a lot of people got use out of at a time when it's like I'm going to build a computer use implementation and I'm going to deal with all the the screenshotting and all the things right that are happening between the messages API. Yeah, we were there for the hackathon that you guys launched at office.

99:11 >> Yeah. and like that was the era when you like needed to have that sort of thing and now you know it's much more about we have a skill like the cloud API skill. It's like really really excellent at helping you either within cloud code or any other coding agents to build a really high quality integration. And now like these sorts of things like I'm going to build a computer use integration like how do I go about doing that? Like very few people I I think sl hope are reaching for the big gnarly cookbook and more so they're loading up the skill in a coding agent and working >> or they're just putting it into a reference architecture. It actually does much better like increasing we're seeing that for a lot of the things that you might want to have different implementations on typically at the harness layer but there could be other variants you just point cloud at and you say this is the reference architecture I want. Yeah. Then you build it. Fun fact, the cloud API skill that helps people build against the API is owned by our Devril team. so that was built by Lance, right? Exactly. Like most high leverage form of DEL is to like distill everything that is best practices that's going to go into those agents.

100:11 >> Yeah. >> One of the reasons it's weird because I'm regarded as this like DEL person authority, but I like it's this like there's some part of me that just wants to tell you you don't need Devrell. >> It's so good you don't need it. >> Right. or right you turn the engineers the the the leaders into the public faces because all you really are trying to do is public faces and like here's how we do things here and then that's kind of it you're need like you know to people will hear about you so like there I think to me when Boris came burst onto the scene like it seemed like a very like hey I'm Boris I'm the creator of Cloud Code blah blah blah this how we do things blah blah you like yes he has the day job but he's also doing that fun functionally so like why why Doesn't everyone just do that?

100:54 >> Yeah. I mean, it's a really good question and there are teams that have done this really well. like I think the Cloudflare team is a really great example. They're all awesome, right? Nontop. >> Yeah. >> And to me, that's actually, by the way, it's a very visible sign of a good manager is that they're all happy at their jobs. They're all they all like publicly identifying. They're not quitting. None of >> them. Totally. It's interesting because I think this is actually something we are trying to do more of with the platform team and with our team and and folks who you know can kind of just get out there and like be part of the community and and be speaking and be onx and be wherever they are, right? I think the problem for us is just like having time and kind of knowing the right way to do that stuff at high quality. So I I see the Devril team in some ways as just being like the experts in doing this sort of stuff at quality. they can do it all day every day and they can help enable the rest of the team to think about how to do this with the small amount of time that they are able to spend on this sort of stuff to do it at high quality too.

101:52 >> Yeah. So like Yeah. So I call this like kind of the unbundling of their row into a front office and a back office. So like a typical person who does this job does the whole thing start to finish. They're kind of autonomous. But actually, you can sort of build out this back office that lets your product leads and engineering leads actually take the spotlight with a simple contract of like, okay, you sit down with me for 30 to 60 minutes and we'll do the brain dump and then you're done. You go back to work and then we'll like we'll like go ghost write for you, whatever. but like that team of like production people, writing people, whatever is sort of provides the service the rest of rest of people and I I think that to me that's like kind of the future of of this of this stuff to be honest.

102:33 because people like don't actually really want to hear from Devrell. They want to hear from N. and and like you know you know and you have like lots of you have t you know and Lydia you got Lydia through bud you know. Exactly. But like he he like functionally he does the job. He does the job. and so like that you want more of those people people want to hear from people in the product, not not like who are like paid paid paid spokesperson which I get a lot of and like that's fine that's a job somebody has to do it then like >> reasonably you can expect people who are working on engineering to not be good at it. Yeah.

103:09 >> So like you should pay someone who specializes in it like specialty is is a skill. But I think there is a back office front office separation that that can emerge. >> Yeah. That is really cool. >> Yeah. And and my analogy would be like everyone hires but you have an HR department. HR department enables you to hiredeed. >> You hire like >> Yeah. >> makes a ton of sense. >> cool. That was my soap box. you know, closing questions. You've been very generous of your time. Any parting thoughts or calls to action?

103:37 >> Something cool on what's something people should try to push the bounds with new Opus 55. You guys have been using it for the longest. >> Yeah, I mean it's really costefficient. it's less verbose. All the things we mentioned, the vibes are really, really high. It's been fun. I yesterday was a really fun day for us cuz like finally, again, I got like a a whole slew of texts from friends and and people who were just like, "Amazing model. Thank you." Like one of my old bosses messaged me and he was like, "Oopus 55 just saved our butts in an incident, right?" And it's like, "Okay, great."

104:08 Like we're we're back is really the energy that we feel. And so I think things that like maybe you wanted to experiment with something and like cost was something that was front of mind for you, right? And like token efficiency and these sorts of things like that kind of might have held you back from like really like firing it off and like letting a model run. I think that's the those are the sorts of problems you should return to now with Opus 55 because I think you'll be able to get like a lot further than you maybe otherwise would have been able to with models that were less cost effective.

104:38 I think you should try something with like a multi- aent setup. I think you will find it to be very good. >> Any any other hints by the way? I mean, MOS is just very broad. >> nope. I think I'd be very curious to hear what people build. but yes, that it's it should be extra good. So, >> yeah, including let's say roles that are not strictly defined, but they assign among themselves, >> right? Which is to me the new thing like you can assign roles, you could always assign roles, you can give tokens jobs. but this is like they're giving themselves jobs.

105:08 >> Yes, >> I guess. say more on multi- agent, right? Like should we use sub agents? What do you how should people think about multi- aents? >> This is pretty good in the sense of like basically generally you want to have one lead and you want to like split up like a bunch of different stuff and as long as you can have a task that you think could be generally paralyzable and they share uniform context across it, I think you will get a lot of gains. Now, of course, it depends on the problem that you're pushing at, but like increasingly this is a very superior way for us to handle a lot of these things. And especially if every sub agent is or whatever you want to call these like sub leads, they are asynchronous and they're not blocking of each other. That is like the only two bits I would say you should care about in your architecture. Other than that, like let it rip and like see what Cloud designs for you. And increasingly, I think a lot of this architecture stuff will fall into this direction. Like cloud will get smarter and smarter. It's going to learn how to figure ways to like split itself, clone itself, adjust itself to the architectures that make sense. You just need to prevent it. You just need to make sure it can like parallel process.

106:08 So, it needs a sh state and it needs to like not block its sub agents. And as long as you contain those two principles, honestly, I think people should experiment and probably try some really crazy stuff. And I wouldn't be surprised to see some like really interesting things on top of that that maybe they felt like there was some intractable problem that was really annoying and they keep pushing for that something like this could actually probably just like crush in maybe one shot or something.

106:29 >> Excellent. All right, everyone go build. >> Cool. Cool.

Summary

Anthropic is gearing up for its IPO with a focus on efficiency and innovation in AI. The company has demonstrated significant growth, achieving a remarkable revenue per employee increase and reporting its first profitable quarter. The podcast discusses Anthropic's strategic approach to AI model development, particularly the launch of Opus 5.5, and emphasizes the importance of efficient cloud infrastructure and user engagement.

- Anthropic's IPO is anticipated to be valued at $2 trillion, with a lifetime cash raise exceeding $100 billion.
- The company has improved its revenue per employee from $1.4 million to $6.6 million in just one year.
- Anthropic has reported its first profitable quarter with a 19% GAAP profit, a significant turnaround from a loss of 129% a year prior.
- The company utilizes two key loops: an improvement loop and an investment loop, driving continuous efficiency and growth.
- The cloud platform is central to Anthropic's strategy, providing customers with tools to build and scale applications efficiently.
- The launch of Opus 5.5 is seen as a major milestone, with positive feedback highlighting its performance and cost-effectiveness.
- The podcast emphasizes the importance of user feedback and collaboration in refining AI models and enhancing user experience.
- Anthropic is focused on developing a strong developer relations team to engage with the community and promote its platform effectively.

Questions Answered

What is the significance of Anthropic's IPO?

Anthropic is launching an IPO with a valuation of $2 trillion, showcasing its rapid growth and efficiency in the AI sector. The company has raised over $100 billion while maintaining a low burn rate, indicating strong financial health.

How does Anthropic ensure effective product and engineering collaboration?

Anthropic fosters a collaborative environment where engineers are product-minded and product managers are technically skilled, allowing for a comprehensive approach to product development and user experience.

What steps are involved in launching a model at Anthropic?

The model launch process includes customer feedback, safety testing, internal evaluations, and an early access program for select customers to ensure quality and performance.

What strategies does Anthropic use to enhance their AI models?

Anthropic employs a simple harness layer for AI models, allowing for hill climbing strategies that optimize performance. This includes innovative approaches like the 'dreaming' system that enhances model capabilities.

How does Anthropic manage its cloud computing resources?

Anthropic utilizes multiple cloud providers to run its operations, experimenting with different compute shapes to optimize performance and scalability across various workloads.

What challenges does Anthropic face in user experience design?

Anthropic encounters difficulties in creating effective routing logic for tasks due to the complexity and variability of user needs, which complicates the user experience.

What are the communication challenges faced by team members?

Team members often find themselves overwhelmed by communication demands, which can detract from their ability to produce meaningful work and focus on critical tasks.

© transcribe · For agents Built with care and craft by Gokul Rajaram