Skip to content
AnthropicAnthropic

Building the future of agents with Claude

Anthropic’s Alex Albert (Claude Relations), Brad Abrams (Product) and Katelyn Lesse (Engineering) discuss the evolution of building agents with Claude, the latest Claude Developer Platform features, and why agents perform best when developers “unhobble” their model with tools. Learn more about the Claude Developer Platform: https://www.claude.com/platform/api 00:00 - Introductions 00:30 - What is the Claude Developer Platform? 2:30 - What is an AI agent 3:15 - Building frontier intelligence for AI agents 4:00 - Reducing model scaffolding to build better agents 5:05 - The evolution of agentic frameworks 6:40 - Unhobbling the model with tools like web fetch 8:35 - Building agents with the Claude Agent SDK (formerly the Claude Code SDK) 10:50 - Best practices for identifying agentic use cases 11: 40 - Driving better agentic outcomes with the SDK 14:35 - Best practices for managing context and memory with Claude 19:00 - The future of the Claude Developer Platform (observability, computer use, and other ways to unhobble the model)

Brad AbramshostAlex AlberthostKatelyn Lessehost
Oct 2, 202522mWatch on YouTube ↗

EVERY SPOKEN WORD

  1. 0:000:30

    Introductions

    1. BA

      'Cause as a developer, like, my creativity ends at some point.

    2. AA

      Yeah.

    3. BA

      I can only think of so many use cases.

    4. AA

      Right.

    5. BA

      But the model, like, anything, anything somebody comes with, the model will figure out a way-

    6. AA

      Right

    7. BA

      ... to go do that thing. [upbeat music]

    8. AA

      Hey, I'm Alex. I lead Claude Relations here at Anthropic. Today we're talking about building the future of agents with Claude, and I'm joined by my colleagues.

    9. BA

      I'm Brad. I run the PM team on the Claude Developer Platform.

    10. KL

      I'm Katelyn. I lead the Engineering team for the Claude Developer

  2. 0:302:30

    What is the Claude Developer Platform?

    1. KL

      Platform.

    2. AA

      Let's talk about the Claude Developer Platform. [chuckles]

    3. BA

      Yeah, let's start with that.

    4. AA

      Uh, let's start with that.

    5. KL

      Start there.

    6. AA

      It used to be called the Anthropic API.

    7. BA

      Yeah.

    8. AA

      We just went through a big name change.

    9. BA

      Yeah.

    10. AA

      Can you walk me through why we made that change, and also what this new platform is and what it encompasses?

    11. KL

      Yeah, totally. So the Claude Developer Platform really encompasses our APIs, our SDKs, our documentation, all of our experiences within the console, and really everything that a developer needs to actually build on top of Claude. We're really humbled, proud to serve, um, some really awesome customers around the world who are trying to, what we like to say, raise the ceiling of intelligence-

    12. AA

      Right

    13. KL

      ... um, using Claude. Um, and the platform really enables them to do that. Um, and I would say one of my favorite parts about it is the platform doesn't just serve customers, uh, externally, the platform actually serves our internal product.

    14. AA

      Mm.

    15. KL

      So, um, we love telling people, like Claude Code, for example, is actually built directly on our public platform.

    16. AA

      I see.

    17. BA

      Yeah. I mean, uh, I think when we started, we were just the Anthropic API, and very simple access to the model. But over the last year or so, we've added so many features to it. Um, we added prompt caching, we added a whole separate batch of API, uh, we added web search, a web fetch, we have this context management support, the code execution. So all these tools-

    18. AA

      Yeah.

    19. BA

      Now, you know, now it's kind of we feel like, yeah, it's aspirationally where it's re- it's a platform now.

    20. AA

      I see. So there's just a lot more to it now.

    21. BA

      Yeah.

    22. AA

      It's evolved in pretty drastic way over the past year, and-

    23. BA

      Yeah. Yeah, I think so

    24. AA

      ... better naming.

    25. BA

      Yeah.

    26. AA

      Um-

    27. BA

      And I think that's what developers were sort of calling it anyway.

    28. AA

      Yeah. Yeah.

    29. BA

      You know, so it's always natural to just sort of go with what developers are saying.

    30. AA

      Right. We were a little late to the game there.

  3. 2:303:15

    What is an AI agent

    1. BA

      Yeah. I mean, agents is... It's almost sort of a buzzword, right?

    2. AA

      Yeah.

    3. BA

      Like, everybody you talk to now is building agents, and, and whenever a industry tech term gets to that level, you know, the definition gets very gray, everything everybody builds is an agent. But Anthropic, what we really think about a agent is where the model is taking some, uh, autonomy to be able to choose what tools to call, to call those tools, to handle the results, and how to choose the next step. So, uh, as a, as a foundational research lab, like leaning into the model and be, and, and what it, its reasoning, how it decides what to do, we think that's a really important element of what an agent is.

    4. AA

      Mm. So it's kind of like the, the aspect of it being autonomous in some sense.

    5. BA

      Yeah.

  4. 3:154:00

    Building frontier intelligence for AI agents

    1. BA

      Yeah. Yeah.

    2. AA

      Charting its own course.

    3. BA

      I mean, I think there's also re- I mean, we have customers doing really useful workflows where they're sort of predefining the path that Claude-

    4. AA

      Mm-hmm

    5. BA

      ... should walk, and that, that is a super useful thing to do. But what's nice about the agentic thing is as the model gets better, every couple of months, you know, we release a new model, and it- with a true agentic pattern, you know, those services are just gonna get better. Where, where if you build a workflow with a lot of scaffolding in it, you kinda put bounds on the model-

    6. AA

      Mm

    7. BA

      ... which is maybe okay in some use cases, but that means that you're- you may not take advantage of the next level of intelligence that a next model release gets.

    8. AA

      Yeah. So it seems like there's this interesting trend with agents, at least over the past 6 to 12 months-

    9. BA

      Mm-hmm

    10. AA

      ... where, like you've said, the scaffolding

  5. 4:005:05

    Reducing model scaffolding to build better agents

    1. AA

      has been-

    2. BA

      Yeah

    3. AA

      ... a bit of a hindrance, and maybe we're dropping some of that.

    4. BA

      Mm-hmm.

    5. AA

      Um, can you explain the intuitions behind that around is, is this actually the future? Is like we give less and less things to the model?

    6. BA

      Yeah. I mean, I think over time what we're seeing is the scaffolding the model needs to be able to accomplish tasks is, is it's needing, it's needing less. As the, as the level of intelligence of the model goes up, and we have every... we believe is gonna keep going up-

    7. AA

      Yeah

    8. BA

      ... um, that basically the model has more contextual understanding of the high level task that it's trying to accomplish, so therefore it doesn't need as many sort of guardrails.

    9. AA

      Right.

    10. BA

      And in fact, those guardrails in some cases become some, uh, like a liability to have. Uh, we've had customers try out new models and say, "Oh, well, it's actually only just a little bit better." And then we kinda look into it with them about what's going on, and it turns out, well, yeah, they were constraining it in ways that makes it harder for them to see the intelligence of the model.

    11. AA

      Ah. Does this match what we see in the field with, like, our customers where they're also following these

  6. 5:056:40

    The evolution of agentic frameworks

    1. AA

      same trends? I know at the limit we have customers exploring all sorts of innovative techniques for managing Claude.

    2. KL

      Yeah, totally. And there's actually a lot of, like, discourse about this right now, right?

    3. AA

      Mm-hmm.

    4. KL

      Like, what is an agent and, and what does it need, what do you need to build? And, and there are people saying, you know, "It's just a while loop."

    5. AA

      Yeah.

    6. BA

      Right.

    7. KL

      Like, you don't have to try that hard.

    8. AA

      Yeah. Right.

    9. KL

      And, um, I think ultimately, uh, there's a lot of, there's been a lot of evolution of frameworks that-

    10. AA

      Mm

    11. KL

      ... people are putting around the model that are helping them orchestrate their agents, try to get the most out of the model. And, um, I think what, uh, the industry is maybe kind of circling around is a lot of that has become maybe too heavy-

    12. AA

      Mm

    13. KL

      ... and maybe too opinionated, um, and which is why you kinda get the, the people coming back to, like, "It's just a while loop, and that is all you need." Um, and I think what we're trying to, to do there is to say-

    14. BA

      Maybe in a lot of ways it is a while loop, but the things we can more uniquely do to help people get the most out of the model is a lot of those tools, those features, and otherwise.

    15. AA

      Mm-hmm.

    16. BA

      And so what we wanna do is put, um, you know, frameworks and tools and platform out there that is opinionated to some extent-

    17. AA

      Mm-hmm

    18. BA

      ... on how people should use those tools. Um, but it's not this like super heavy framework that really like, to Brad's point, gets in the way-

    19. AA

      Mm-hmm

    20. BA

      ... of what the model's ultimately trying to do. So to strike the right balance, it's like, you know, we've, we've seen what a lot of people have tried to do, so we know we can be opinionated there, um, but we wanna be lightweight [chuckles] in the way that we're doing that-

    21. AA

      Right

    22. BA

      ... and make sure that the real thing we're doing is helping you get the most out of the model, um, without, you know, bogging you down in some super heavy framework.

    23. AA

      Right. So would you describe part

  7. 6:408:35

    Unhobbling the model with tools like web fetch

    1. AA

      of the strategy here then as providing these auxiliary tools and things that we can give to the model-

    2. BA

      Mm-hmm

    3. AA

      ... but we're not necessarily, like, placing the bumper-

    4. BA

      Right

    5. AA

      ... spawn, like the model itself or-

    6. BA

      Yeah. We think about, we think about it as like, how do you unhobble the model?

    7. AA

      Unhobble, yeah.

    8. BA

      Like, the model already has a lot of capabilities, and in fact, I'm convinced that even if you take a current generation of models, there's way more intelligence in there than we've been able to unlock.

    9. AA

      Mm.

    10. BA

      But anyway, that intuition is if you just give the model, like, the tools it needs, and like set it, set it free-

    11. AA

      Mm-hmm

    12. BA

      ... let it be able to use those in the right way, um, you'll get great results.

    13. AA

      Mm.

    14. BA

      And, and I think like a good example of that is we launched this server side, uh, web search tool and we- and web fetch tools, and it's been interesting to watch customers use those. And, you know, all we did real... I mean, it's a very minimal prompt that we have. We just give it the web search tool, and, like, all of a sudden, deep research tasks are, like, almost completely done-

    15. AA

      Mm

    16. BA

      ... with, with just turning on that, uh, switch on the API because the model will call that tool, it'll look at its results, it'll say, consider it, and say, "Okay, maybe I need to call, you know, do these other searches."

    17. AA

      Right.

    18. BA

      And then, "Oh, that fourth link you returned, that's the great one."

    19. AA

      Right.

    20. BA

      It'll do a web fetch on that link and bring that data back, and really all that very autonomously on its own kind of deciding.

    21. AA

      Right. I, I think it's almost kind of like an interesting shift in, like, where the intelligence of a system is being applied.

    22. BA

      Exactly, yeah.

    23. AA

      From like the developer having to apply their intelligence to guiding-

    24. BA

      Right

    25. AA

      ... towards like the model now-

    26. BA

      Right

    27. AA

      ... figuring it out.

    28. BA

      And it's so exciting when the model does it because as a developer, like, my creativity ends at some point.

    29. AA

      Yeah.

    30. BA

      I can only think of so many use cases.

  8. 8:3510:50

    Building agents with the Claude Agent SDK (formerly the Claude Code SDK)

    1. AA

      the developer platform, what do you recommend? What are some best practices or ways for me to get started?

    2. BA

      Yeah. So, um, super tactically, actually, the number one thing that we recommend right now is the Claude Code SDK.

    3. AA

      Mm-hmm.

    4. BA

      Um-

    5. AA

      Okay

    6. BA

      ... and what's really, really interesting about the Claude Code SDK is we essentially built an agent harness, an agentic harness, um, around the model to run that loop, right, and automate a lot of that tool calling and otherwise feature use. And obviously, originally was built for coding purposes. Um, and what, uh, the team really quickly figured out was like, actually, this is like an excellent general purpose- [chuckles]

    7. AA

      Mm-hmm

    8. BA

      ... agentic harness. Um, and so what the SDK does is it gives people a perfect out-of-the-box solution to actually just start prototyping agents-

    9. AA

      Mm

    10. BA

      ... um, without having to go and build, you know, the loop with all the tool calling and otherwise. It's built on top of the messages API and all those same tools that, um, we're mentioning, but it kinda gives you that really great starting place right out of the box.

    11. AA

      Right. I feel like this is a pretty common misconception, at least when I talk to developers, about the Claude Code SDK.

    12. BA

      Mm-hmm.

    13. AA

      So like, I'm not building a coding application.

    14. BA

      Mm-hmm, mm-hmm.

    15. AA

      Like, why would I wanna use this?

    16. BA

      Yeah.

    17. AA

      Mm-hmm. But you can kind of remove the coding-specific-

    18. BA

      Yeah

    19. AA

      ... parts, right?

    20. BA

      Yeah. I mean, I think that's a great example of what we were talking about, removing scaffolding on the model. It's like once we got done removing things-

    21. AA

      Mm-hmm

    22. BA

      ... from the Claude, from Claude Code to really unhobble the model, it turns out there was [chuckles] nothing coding left.

    23. AA

      Right.

    24. BA

      When the, when you remove everything else, then it's just an agentic loop, and you're, you're really a minimalistic thing to give, uh, Claude access to, to a file system-

    25. AA

      Yeah

    26. BA

      ... to a set of like Linux command line tools, um, to the ability to, you know, write code and execute that code. So those are all very generic kind of-

    27. AA

      Right

    28. BA

      ... capabilities that turns out could solve a wide variety of problems.

    29. AA

      Right. Yeah. I feel like something I've been running up to in like my own side projects and also seeing with-

    30. BA

      Mm-hmm

  9. 10:5014:35

    Best practices for identifying agentic use cases

    1. AA

      think that's super interesting.

    2. BA

      Yeah. I mean, I think, I think the other really interesting to- thing to think about, especially for businesses looking at a- agents, is like, what use case to go target.

    3. AA

      Right.

    4. BA

      So, uh, thinking beyond the technology, like, what is the actual problem to go solve? And I, I, I think, you know, we've s- we see a lot of customers and like doing a lot of things. We love all of it, but where, you know, the biggest impacts are is where the customer has thought hard about what's the business value of this.

    5. AA

      Mm.

    6. BA

      Like, will it actually save this many engineering hours, or will it help us remove this much, uh, uh, manual work or whatnot? And being able to articulate, like, what you expect the outcome of the agent project to be, I think is really helpful in, in defining the scope, uh, of the agent.

    7. AA

      Right. And t- tying back one more time to the SDK, so it seems like-

    8. BA

      Yeah

    9. AA

      ... it's been really, really useful for, like, individual developers like myself-

    10. BA

      Yep, yep, yep

    11. AA

      ... you know, starting out-

    12. BA

      Yep

    13. AA

      ... and just wanting to get hacking on something really fast. For these customers, for enterprises that are actually trying-

    14. BA

      Right

    15. AA

      ... to get real business value-

    16. BA

      Right

    17. AA

      ... out of these things, should they be using the SDK? Is it ready for them? Is it ready for scaled use like that?

    18. KL

      Yeah. So, um, I think in a lot of ways it is. In a lot of ways, if you are in a spot where you can... Like, you can deploy that runtime. Essentially, that's what you get out of the SDK-

    19. AA

      Yeah.

    20. KL

      -is an agentic loop runtime. Um, you can go and deploy that runtime wherever you want, [chuckles] whenever you're ready to do so. But I think what we're really trying to do is take the spirit of what the SDK unlocks for people, like go kind of up to that higher order abstraction where we give you the loop, we give you a lot of the tool calling in an automated way, um, and say, "How can we learn from that and give people out-of-the-box solutions that, like, at scale-"

    21. AA

      Mm-hmm.

    22. KL

      -um, will really be able to solve for their use cases?" And I think that's a lot of where we're kind of trying to go with our roadmap throughout the rest of the year. Um, and one really important bit when we think about that is if the entire goal here is to help our users, like, really raise that ceiling of intelligence, get the absolute best outcome out of the models, then higher order abstractions are not just make it easier because you don't have to write all that code yourself. It's actually, like, how can we, like, really truly help you get the best outcome-

    23. AA

      Mm-hmm.

    24. KL

      -because we, uh, we're in the room with research, we're in the room with inference. Like, we know how to make sure that our abstractions, our agentic loop is going to be, uh, extremely powerful-

    25. AA

      Right.

    26. KL

      -and extremely good at working with Claude. Um, and the last thing that I would add in there is especially as these things get longer running, and as we provide more and more tooling to help people get at those longer running tasks, um, another big problem that our users we know are gonna keep trying to solve is, uh, observability within-

    27. AA

      Mm-hmm. Mm-hmm.

    28. KL

      -those longer running tasks. Um, and so that's, that's one of the most common things that comes up for folks is, you know, I, I have these long-running tasks, I'm trying to get, um, these really great outcomes. But, um, you know, I might need to do some steering, or I might need to tune my prompt, or I might need to think about tool calling a little differently. And, um, that's something that we know we can give people that observability through the platform over time-

    29. AA

      Mm-hmm. Mm-hmm.

    30. KL

      -and that's another big area of focus for us.

  10. 14:3519:00

    Best practices for managing context and memory with Claude

    1. AA

      of how-

    2. BA

      Hmm.

    3. AA

      -we're gonna address that. Um, before I do, uh, is there other tools that exist right now that folks should be aware of when they're getting started with the developer platform? Things have... you've found helpful or useful?

    4. BA

      Yeah. I mean, I think there's a c- so we mentioned, uh, web search and web fetch. Uh, I think an-another big thing that we're seeing is, um, customers, m- uh, have to do... right now have to do a lot of work to manage the context window. So by default, Claude has 200k tokens of context. We have a mil-million token available now in beta on Sonnet, which is great, but even a million, there's a limit there. Uh, and what, what many customers have told us is that, um, they get better outputs, higher intelligence if they, uh, even use a smaller part of the context. And so we've done... We have a, a couple of cool features that are just coming out to help developers manage that context.

    5. AA

      Hmm.

    6. BA

      So in these agentic loops, a lot of times you're doing ten, 15, 100 tool calls, and you edit this file or look up data in this database or, uh, you know, send this email, and each of those tool calls takes up like a, you know, 100, 200, 1,000 tokens.

    7. AA

      Right.

    8. BA

      Uh, and so we have this cool feature that lets you, uh, lets the model actually remove some of the older tool calls that are not needed anymore.

    9. AA

      Interesting.

    10. BA

      Uh, and that give, that gives just, just like you, if you declutter your desk and declutter your notebook-

    11. AA

      Yeah.

    12. BA

      -like, you can focus a little bit better. So if you declutter the prompt, actually, the model can actually focus a little bit better.

    13. AA

      Oh, interesting. So okay, we're removing unnecessary context.

    14. BA

      Mm-hmm.

    15. AA

      Is there a risk that we remove necessary context?

    16. BA

      Yeah.

    17. AA

      How does that work?

    18. BA

      Yeah, yeah. Yeah, yeah. So, um, we have some, some guardrails and some-

    19. AA

      Okay.

    20. BA

      -bounds around it, so you don't... But g-the general rule is if you, um, remo- we try to remove the tools that are, like, several turns back.

    21. AA

      Okay.

    22. BA

      That the model's already made decisions based on those tools. But if you... AI was playing with it, uh, recently, and r-I removed the tools that it was just called-

    23. AA

      Mm.

    24. BA

      -and it's, "Oh, my tool results are gone. I don't know what to do."

    25. AA

      Right.

    26. BA

      And then the... but the mo- the Sonnet doesn't give up. Like, it's like, "I'm just gonna call this tool again."

    27. AA

      Yeah.

    28. BA

      You know?

    29. AA

      Yeah, yeah, yeah.

    30. BA

      Um, but yeah. So generally, we have put some bounds on that because of that experience. So we, we do preserve the most recent set of tools.

  11. 19:0022:10

    The future of the Claude Developer Platform (observability, computer use, and other ways to unhobble the model)

    1. AA

      here. So it sounds like there's a ton of new features that we've recently launched. There's a lot of momentum, and now there's other offerings as well, like the Claude Code SDK-

    2. BA

      Mm-hmm

    3. AA

      ... and things coming out soon. Um, what are you most excited about, Katelyn? What's the, what's the future looking like here in the next six to twelve months?

    4. KL

      Yeah. So we talked a little bit about these higher orders of abstraction where we can, um, really just make it, uh, as, as simple as possible for you to get the absolute best outcomes out of Claude. Um, and we wanna pair that with the observability that we talked about, um, so that you can really like, you know, see the data and take those insights from those longer running tasks. Um, and if you combine these things together and start to think about some of the capabilities like memory that Brad just talked about, you can really start to see this flywheel where over time, we're not just able to help you get the best outcomes out of Claude, but we can help you get self-improving and continuously-

    5. BA

      Mm. Mm-hmm

    6. KL

      ... improving outcomes out of Claude. And that to me is kind of the, the like galaxy brain magic of the roadmap, is get to a point where, um, you know, we, we have people coming to us, they're building on Claude, they're, they have their tasks, they know what they're trying to do, um, and they get these like really like aha moments where over time it's getting better and better and better. Um, and you know, that is... that's kind of the biggest thing that in everything that we're doing, we're trying to make sure we're going after.

    7. AA

      That's awesome.

    8. BA

      Yeah, I mean, I guess I'd have to say I'm a- I, I'm always excited about model launches.

    9. AA

      Yeah.

    10. BA

      Like, it's like Christmas, like what, how, what will, will it, what will be possible now? So I love playing with the model launches as they come out, just unlocks more use cases. Some use cases that, you know, we've been working hard on and, and trying to improve, which is satisfying to see, but also some things, oh, we had no idea the model would be able to do this thing.

    11. AA

      Right.

    12. BA

      You know, now it draws ASCII pictures so much better.

    13. AA

      Yeah [laughs] .

    14. BA

      Or what, you know, whatever.

    15. AA

      The important things [laughs] .

    16. BA

      The very important things. But beyond that, the other thing I'm really excited about is, um, we're, we're in the early stages of giving Claude a computer. You know, I think about if we, uh, hire an employee here at Anthropic, and we, we welcome them, "Here's your first day," but we don't give them a computer.

    17. AA

      Yeah.

    18. BA

      Like, they would not be very successful [laughs] at Anthropic.

    19. AA

      Right.

    20. BA

      So like right now, essentially everybody u- is using Claude and, and it doesn't have a computer. So I'm, I'm really excited about giving Claude a computer, and I... you see like the very baby steps of that-

    21. AA

      Mm-hmm

    22. BA

      ... with the code execution tool-

    23. AA

      Mm-hmm

    24. BA

      ... uh, where the, the model can write code, execute it on the VM, and get the results back. So like it can like zoom in on images or take a, a Excel spreadsheet and create like amazing data analysis with charts and graphs, and that's just the baby step. Like, what if it had a persistent computer-

    25. AA

      Right

    26. BA

      ... that was always there and it could like organize the files in there the way it needed-

    27. AA

      Yeah

    28. BA

      ... and get the tools set up the way it wanted and, um, I just think there's a lot of headroom-

    29. AA

      Right

    30. BA

      ... to, to that scenario.

Episode duration: 22:10

Install uListen for AI-powered chat & search across the full episode — Get Full Transcript

Transcript of episode XuvKFsktX0Q

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.

Add to Chrome