Context Engineering Our Way to Long-Horizon Agents: LangChain’s Harrison Chase

People use traces from the start to just tell what's going on under the hood. And it's way more impactful in agents than in single LLM applications because in single applications you get some bad response from the LLM. You know exactly what your prompt is, you know exactly what the context that goes in is because that's determined by code. And then you get something out in agents. They're running and repeating. And so you don't actually know what the context at step 14 will be because there's 13 steps before that that could pull arbitrary things in. So like what exactly is everything's context Engineering. Context engineering is such a good term. I wish I came up with that term. Like it really describes like everything we've done at LangChain without knowing that that term existed. But like traces just like tell you what's in your context. And that's so.

Welcome to Training Data. Harrison, you were our very first guest on Training data and the AI space has moved so quickly in the 18 months or so since we originally interviewed you. And so I'm delighted to get you on the show today. Topics of the moment. I think there's nobody better than you to talk about some of these topics. We're going to talk first about Long Horizon agents and agent harnesses. Pat and I had this blog post on this yesterday. I know this is something that you are deeply fluent in. And then we're going to talk about what's the difference between building Long Horizon agents versus building software and the role that you see LangChain playing in that ecosystem. And then finally I just want to chat with you about the future. I think you single handedly saw the agent opportunity. I think before anybody. We were back in the GPT three days and I think you see the future for what's happening with agents. And so I'm just excited to chat with you open endedly about the future as well.

I am really excited as well. Thank you guys for having me back. It's quite an honor. I'll tell my mom again that I'm.

Back on the Hub. Wonderful. Okay, let's start with Long Horizon agents.

Yes, that was a great term. You guys wrote a great article.

Sony's good at naming things.

We're not going to get into the backstory there.

What do you think?

What do you agree with? What do you disagree with?

I mean, I agree that they're starting to finally work. I think the idea of running an LLM in a loop and just having it go was always the idea of agents from the start Auto GPT was basically this. Then this is why it took off and captured so many people's imagination, because it was just an LLM running in a loop, completely deciding what to do. The issue is the models weren't really good enough and the scaffolding and harnesses around them weren't really good enough. And I think the models got better. We learned more about what makes a good harness over the past few years and now they start to really, really work. And you see this in coding first. And I think that's the domain where they're taking off the most and that's spreading to other domains. But you can give a task to an agent and you still need to communicate to it what you want it to do. And it needs to have the right tools and all of that, but it can actually operate for longer and longer periods of time. And so the long horizons, kind of like framing of it, I think is really, really apt and really, really good.

Awesome. What are your favorite examples of Long Horizon agents? And I guess what shapes do you see them taking?

So coding's the place where there's the most. I think that's the one that I probably use. Yeah, that's the one that I use the most. Adjacent to that, I think, like really good ones are AI SREs. So traversal, I think, is a Sequoia company and they have an AI SRE that that operates over longer time horizons. Research in general, and I'd call AI SRES kind of research. They're taking an incident and they're going and digging through logs. Research in general is a really, really good task because it ends up producing like a first draft of something. And the issue with agents is they aren't reliable to nine nines of reliability, but they can do a ton of work and more and more work over longer time horizons. So if you can find these framings where they run for a long period of time but produce like a frame first draft of something, those to me are like the killer applications of Long Horizon agents right now. So coding is an example of that coding. You usually put up a pr. You don't directly push to prod unless you're vibe coding, which is also starting to get better and better. Aisres usually surface it to a human who comes in and then reviews it. Report generation, you don't send it out to all of your followers right away. You look at it, you edit it, it creates a first draft of something. So we see this in finance a bunch. This is a huge research opportunity to customer support. We see A lot of things pivoting from kind of like the initial customer support was like first line response, like someone messages. You just respond really quickly and there's still that. And that's going great. But now there's examples. Klarn is a great example of this where it's like humans and AI working together. When the first line fails, you escalate to a human. You don't just have the human handle it. You have this long horizon agent run in the background, produce a report of everything that happened and then hand it off to the, to the, to the agent there, to the human agent there. Agent starts to get confusing in customer support. So I think the killer use case of all of these is places where you have like this first draft type of concept.

And then how much of the why now do you think is the models themselves are just so good versus people are doing really smart things on the harness side. And maybe even before we get to that, can you say a word for our listeners on like, you know, how you frame the harness versus the model in terms of the actual composition of an agent?

Yeah, I'll maybe bring in framework as well, because I think early on, I mean, that's how we describe LangChain. That's what LangChain is. It's an agent framework. And now we have deep agents, which I'd call an agent harness. And we get asked about what's the difference? So a model is obviously the LLMs tokens, messages in, messages out. The framework would be abstractions around that. So making it easy to switch between models, adding abstractions for other things like tools and vector stores and memory and things like that, but pretty unopinionated about what actually goes in there. The values more in abstractions which can be good, can be bad. Harnesses are more like batteries included. So when we talk about deep agents, we're talking about we actually give it a planning tool by default. So it has a tool that comes built into the harness. That's pretty opinionated that this is the right way to do things. We do compaction. So you have these long horizon agents. They're running for long periods of time. Context windows are larger, but they're still not infinite. And so at some point you need to compact that. How do you do that? There's a lot of research going on there right now. One of the other sets of tools that we and a lot of people are giving to these agents are tools for interacting with the file system, whether directly or via Bash. And it's kind of tough to separate from the models, because the models are being trained on a lot of this data as well. And so there's this kind of evolution between. I don't know if we could have known that these file system based harnesses are the best thing. If we go back two years ago, I don't think we could have known that because models weren't really being trained on that as much as they are now. And so they're kind of evolving together. So I think it's a combination of things. The models absolutely are getting better. Reasoning models are helping a lot. But it's also the fact that we're figuring out all these primitives around compaction and, and planning and these file system tools being really useful. And so I do think it's a combination of both.

I remember in that very first episode we did together, you described laying graph, I think as almost the cognitive framework of the agent. Is that the right way to think about what the harness is?

Yeah, I think that's right. Yeah. So we build deep agents on top of Langgraph. It's one particular kind of like Langgraph instance. It's very opinionated. It's more general purpose. And so I think early on we talked about general purpose architectures and more specific architectures. And what we've seen is that a lot of the specificity for tasks previously that might have been in Langgraph because you need to put more structure on the models. Now that specificity is moving into the tools and the instructions. So there's still the same level of complexity. It's just in natural language. And so prompting and editing those prompts and maybe automatically updating those is becoming a part of. But the harness is remaining a little bit more fixed.

What's the hardest thing to get right on the harness side? And do you think, you know, do you think individual companies can actually excel at the harness engineering side of things? Who do you admire there?

I think a lot of the companies that are doing the best harness engineering are coating companies. Honestly, I think that's the place where it's taken off a bunch. I mean, you look at cloud code, I would argue a big reason for the popularity of cloud code is the harness itself.

Does that by the way, imply that harnesses are better built by foundation model companies than by third party startups?

I don't know. The next company I was going to mention is Factory, which is another coding company. And I think you look at the hardness they've done there. AMP is another coding company, has a really good harness. I think there's pros and cons they. There definitely is some aspect of the harness being tied to a model, and maybe not just not a specific model, but a family of models. So all CLAUDE models, like anthropic fine tunes on some specific tools. OpenAI fine tunes on different ones. So I think probably when we were doing this last time, we maybe talked about how prompts need to be different for one model versus another. Harnesses also need to be slightly different for one family of things versus the other. But there are similarities. All of them use the file system in some sense. So I think this is. I actually don't know the answer to that. It's a really interesting thing. We see that a lot of the coding. Everyone who's building a coding company is basically building their own harness right now. And there's all these leaderboards. And you can see it's actually kind of interesting. If you go to Terminal Bench 2, which I think is probably one of the more popular coding benchmarks right now, you can actually see they have the agent harness and then the model. And so you can see the variation in performance. And CLAUDE code is not at the top of that. So there's differences. But I think it doesn't necessarily mean that the model labs are better at it. It just means that you have to understand how the models work. And people who look at what makes a harness tick around the model can get some performance gains there.

What do you think goes into, you know, making the harness tick? Like, what do you think the guys at the top of the leaderboard are doing? Exceptionally well.

I think part of it is definitely understanding, like, what tools the models trained on. So I think OpenAI trains really heavily on Bash. I think Anthropic has some explicit kind of like file editing tools. And so I think leaning into that is part of it. Compaction is becoming more and more of a thing. So especially as you start doing longer horizon tasks, like, you start to fill up the context window and so what do you do? There is a really big question and there's a bunch of strategies for kind of like approach approaching that. I'd argue that's part of a harness. So all of these harnesses, also, this is where skills and MCPS and sub agents start to come into play as well. And you can use those in different ways. And I don't think a ton of skills or sub agents are trained into the models yet. Those are still pretty new. One of the things that we see in our harness is when you have a subagent, the main model needs to communicate with it, like, well, it needs to, it needs to give it all the appropriate information. It needs to let the subagent know that it needs to like give it its final response out. So like we would see some failure modes where the sub agent. Because basically what happens is you kick off a sub agent and then only the final response is passed back to the main agent. And so we'd see some failure modes where the subagent would do a bunch of work and then it would be basically like, look at my work above. And then, you know, pass that back to the main agent and it can't see it and it's like, what are you talking about? And so like that type of like prompting to get these pieces to work together is a big part of it. So like skills, subagents, mcp, there, there are like prompts in all of these harnesses that make them work well or don't make them work well. And there, there are hundreds of, of lines long if you look at some of the, the ones that are out there.

Can I see a question on how this has evolved? And since you've always been really kind of on the bleeding edge of what are people doing around the models to make them work in the real world? Right. If we think about in our simplistic view on what the big inflection points over the last five years have been, it feels like there was a big inflection point around pre training when ChatGPT came out. Feels like there was a big inflection point around reasoning when O1 came out. Feels like just recently there's been a third big inflection point around these long horizon agents with cloud code and opus 4.5. In your world, the world of all the stuff around the models that makes them work in the real world, would you have a different set of inflection points? What have the major changes been? I remember we talked about cognitive architectures a couple years ago and now we're talking about, talking about frameworks and agent harnesses. What are the major leaps in sort of the design around the model? What have they been?

So I think there's maybe like three eras I would say, I'd say like early on and this is when LangChain was just started. Like these were still the raw text in text out, like not even chat based models. And so they didn't have any of the tool calling, they didn't have any content blocks, any reasoning at all. They were really just like really, really basic. And so the things that people were doing were mostly like single prompts or like Chains, and it wasn't even possible to do anything that complicated. Then a lot of the model labs started training in a lot of the tool calling into the models, and they got really good at, or they tried to make them good at thinking and planning, and they still weren't good yet. They sort of weren't good as they are today, but they were good enough to decide what to do. And this is where the custom cognitive architectures would come in more into play, because you'd ask it explicitly, what do I do here? But it was a very point in time. And then you go down this branch and then what do I do here? And maybe there's a loop and there started to be some loops, but it's still a little bit more scaffolding around it. And then there was an inflection point. And I don't know where exactly that was. I would say I think we noticed it probably in June, July of this year, where we saw Claude code taking off, Deep research taking off, Manus taking off. And these all use the same architecture under the hood of just the LLM running in the loop. But, like, cleverly, like, a lot of. A lot of hardness is context engineering. Like everything around contaction, context engineering, sub agents, context skills, context engineering. So we basically saw them using the same core algorithm, but making just like improvements on context engineering. And we're like, oh, that's interesting. That's pretty different than before. And so that's when we started working on deep agents. I think for a lot of people in the coding community, I think probably like Opus 4. 5 was when they started to really feel this. It might have also just coincided with winter break when everyone went home and started using Claude code and realized how good it was. But I think around November, December, I think there has been this, at least I sense a pretty big vibe shift. And people just like, yeah, you throw hard problems at these things and you get long horizon agents. And so I don't know whether it was early 2025 or late 2025, but at some point the models got good enough, and that's when we moved from scaffolds to harnesses.

And what's next on this arc?

I wish I could tell you. I mean, I do think that, like, this algorithm of just running the LLM in a loop and letting it orchestrate its own, letting it really choose what to pull into context and doing stuff there that is like, it's so simple and so general purpose. Like, I mean, that was the core idea of agents all along. And we're finally there, if you look at some of the manual scaffolding, like maybe some of that goes away. So like compaction is still very manual. Like the harness authority decides what to do with it. Anthropic has some interesting things where they let the model decide, like when to compact things. We don't really see a ton of people using that. Maybe that'll be a part that's next. Part of what we're really interested in is memory as well. If you think about memory in the context of this, that's also context engineering. Right? It's context engineering over longer time horizons. And it's a slightly different set of contexts, but it's still giving that to the, to the LLM. And I think, I think the core algorithm is pretty simple. It's run the LLM in a loop and we're finally there and it kind of works. And so I think there'll be a bunch of context engineering tricks around it. And maybe some of that is giving the context engineering actually to the LLM, like the anthropic thing. Maybe some of that is just pulling in new types of context. The models will probably get better. They'll probably get better and better at these types of longer horizon tasks. That'll be great as well. One of the big questions on my mind, so a lot of these harnesses that we see are very coding specific and that's where we first started to really see these long horizon agents take off. And even for non coding tasks, I think you can make an argument that writing code is really useful and can be general purpose.

I was going to ask you, are coding agents? Is that a subcategory or are coding agents just agents? Meaning the job of an agent is to figure out how to get a computer to do useful stuff. And code is a pretty good way to get a computer to do useful stuff.

I don't know. This is one of the big. So I very, very strongly believe that right now if you're building a long horizon agent, you need to give it access to a file system. There's so many things you can do with a file system in terms of context management. When we talk about compaction, one strategy is to summarize but put all the messages in the file system so that if it needs to look it up, it can. Another strategy is when you have big tool call results, don't pass it all to the model. Put it in the file system and let it look it up. Now you can do all of that without like a real file system actually without letting it write Code. So we have a concept of like a virtual file system where it's just backed by postgres or something like that, and it's more scalable. But there are obviously things you can do with code that you can't do with a virtual file system. You can't run code in a virtual file system. So like writing scripts is like really useful for that.

Yeah.

And I think a coding agent can be general purpose, but I don't know if that means that today's coding agents are, if that makes sense. Because I think a lot of the coding agents today are pretty optimized for coding tasks.

Yeah.

And so I think it's possible that a general purpose agent is a coding agent, but I don't know if like the reverse is true. If that kind of like makes sense.

Yeah, yeah, yeah.

We're thinking about that a lot as well. Are all agents coding agents?

Yeah, that's one of the biggest things that we're thinking about right now.

Yeah.

Maybe.

Can we transition into talking about what goes into building a Long horizon agent versus building software? Can you maybe describe the software development stack for 1.0 code development and what's different now? And I thought you had a really good X article on this. Maybe just summarize the punchline.

I think about this a bunch because we like to say that, and I think a lot of people would agree that building agents is different than building software. But what exactly is different? Because I think it's easy and lazy to say that it's different. But what actually is different? These might sound obvious, but hopefully that's good and they're not controversial. But when you're building software, all of the logic is in the code in the software, and you can see it there. When you're building an agent, the logic for how your applications works is not all in the code. A large part of it comes from the model. And so what this means is that you can't just look at the code and tell exactly what the agent would do in a specific scenario. You actually have to run it. And so what does that mean? I think that's the biggest difference. By the way, we're introducing these non deterministic systems into it and it's a black box and it lives outside. And I think all that's true. That's the biggest difference. So what exactly does that mean? I think one thing that that means is that in order to tell what the application is actually doing, you can't look at the code. You have to look at actually what it does in Real life. And so I think one of the things that we do that is most popular is Langsmith. One of the core parts of that is tracing. Why are traces so popular? Because they tell you exactly what goes on inside your agent at every step. And it's different than software traces, where in software you kind of have your system over here and it emits a bunch of like stuff and you, you know, you, you look at it when maybe there's some errors, but you don't need like everything. And you usually only turn that on when you put it in production because if it's local, you just put a breakpoint or something like that. In agents, people use traces from the start to just tell what's going on under the hood. And it's way more impactful in agents than in single LLM applications. Because in single LLM applications you get some bad response from the LLM. You know exactly what your prompt is, you know exactly what the context that goes in is because that's determined by code. And then you get something out. In agents, they're running and repeating. And so you don't actually know what the context at step 14 will be because there's 13 steps before that that could pull arbitrary things in. So what exactly is everything's context? Engineering context. Engineering is such a good term. I wish I came up with that term. It actually really describes everything we've done at LangChain without knowing that that term existed. But traces just tell you what's in your context and that's so important. And so what does that mean? That means that the source of truth for software is in code and for agents it's a combination now of code and traces are where you can see the source of truth. It's technically in all those millions, billions of parameters. But like you can't really do anything with that. So now, so now that means that traces become a place where you start to think about testing. Because now you can't, you can test, you can test some parts still of the harness and you can do some unit testing offline. But like in order to get what the test cases are, you probably want to use the traces to construct that. You probably want to be testing online. That's probably more important in agents than it is in software is online testing. Because behavior doesn't emerge until it's actually being used with, with real world inputs. We see traces becoming a point of collaboration for teams. Because if something goes wrong, it's not, oh, let's go look at the code in GitHub. It's let's go look at the trace. We see this in our open source as well. When people are being like, hey, deepagents went off the rails here. What happened? Our response is, send us a Langsmith trace. We can't really help you debug if it's not that. Previously would be like, show me the code. Right? So there's a transition there. And then I think the other thing that. And so that was the blog post that I wrote on next, which got a lot of good feedback on them and still kind of figuring out how to phrase it, but I think that's a big part of it. The other thing which I'm still trying to think through as well, is I think building agents is more iterative. And we used to say that. And I would kind of roll my eyes because building software is iterative as well, right? You ship it, you get feedback, and it's constant iteration. That's like what it is. I think the difference is that in software, you're kind of like iterating based on what you want the software to do. Like you have some idea, you ship it, you get feedback. Oh, maybe this button is confusing. Maybe users actually want to do X instead of Y. But you know what the software does before you ship it. With agents, you don't know what the agent does before you ship it. You have an idea, but you don't really know what it does before you ship it. And so I think there's way more iteration involved in order to get it like accurate, get it like write and passing conceptual unit tests, basically, and building upon that. This is actually why I think memory is really important as well, because memory is learning from those interactions. And so if now you have a process that's way more iterative, and so now you have to. It's way harder to build as a developer because I have to change the system prompt way more than I would have to change code in order to get it just perform correctly. So that's where memory comes in. Because if there's a way where the system can kind of learn by itself, that cuts down the iteration that you have to do as a developer and makes it easier to build these types of agents. So that's another kind of angle that I absolutely think agents are different than building software. I think it's also a little cliche to say that. And so I've tried to think about what exactly is different. And those are like the two things that have kind of come up with.

Well, and I'm curious on that too. One of the questions this is a big public market debate right now is are the existing software companies going to make it? And if you analogize to an on prem software went to cloud, very few actually did make it because it turned out that building cloud software was actually quite different than building on prem software. And since you're in the middle of kind of how people are building with AI, what's your take on. Not necessarily the public market question, but how different is it? Have you seen a lot of people who kind of were good at building software the old way and now they're good at building software the new way? Or is it more just you either grow up building it the new way or you never get it? Do you think people can make the leap? A lot of young founders out there right now, which makes me think that certainly it seems like the younger people without a lot of preconceived notions on how to build software have the blank slate that has allowed them to pick up on a lot of this stuff.

I do think we have consistently heard that a lot of the people who are on these agent engineering teams are more junior developers, more junior builders even, who don't have those preconceived notions. Our applied AI team internally definitely skews on the younger side, I do think. I mean, in terms of. I think there's, there's like a person aspect to this. There's also like a company aspect to this. Like, I do think that, like, data is still really, really, really valuable. Yeah, I think when you think about this harness, basically there's like, if harnesses become. By the way, I don't think that most people will build their own harness in the long run because it's actually way harder than building a framework. And so I think they'll use a harness from us or from someone else. And so if you think about what goes into that, it's like the prompt and the instructions and then the tools that it's connected to. And I think one thing that this is more at the company level now, but like one thing that existing companies have is all the data and all the APIs. If you've done a good job at that, then I think it will actually be pretty easy to plug those in and get real value out of things. We were talking to someone in the finance space and they are saying, yeah, like the value of data is just going up and up and up and up. So if you're a previous software vendor and you have this data that is valuable, like, you should be able to expose it to agents and get a lot of value out of that.

Yeah.

The other part of it, though, is the instructions on what to do with that data. And that's probably like more net new in terms of like how to use that data. That's probably. You probably had some ideas about that as a software vendor, but you didn't kind of like consolidate it. You didn't have it because that was something that humans would still do, like a lot of what agents are doing or humans would still do. So you'd give them the tools to do it, but you wouldn't have tried to like automate that or you wouldn't have successfully automated it before. Kind of like agents. And so that part, I think is newer and we're also seeing a lot of demand, like I think a lot of the vertical startups. Rogo is a great example of someone who has experience in finance and is bringing that knowledge to agents. And the reason that's kind of like effective is because a lot of the agents are driven by knowledge and not like world knowledge, but like knowledge on how to do specific patterns. So kind of, yeah, I think there's like. Are the people who are building software the right people to build agents? I think we saw a lot of really senior developers adopt agentic coding. And so I think it's a mindset thing. But yeah, there is maybe a younger skew there and then for companies, depends on the data.

Yeah, even Pat's on cloud code, so yeah, even those guys can get it.

Sonia got me on there.

Okay, so it seems like the trace is a core artifact, you think, in kind of this new world of agent development. And it's something that Langsmith helps a lot with. What other core artifacts do you think are there? And specifically, I'm wondering about evals.

Yeah, I think maybe artifact is the wrong word. Components. Components, yeah. I mean, I think one other thing that is different between building software and building agents is that to evaluate software you could pretty reliably, you could rely on tests and assertions of things programmatically. With agents, a lot of what they're doing is things that humans would do. So in order to judge them, you need to bring human judgment into that. And that's another thing that we try to do in Linksmith is how can you bring. You've got these traces. How can you bring human judgment to them? And so that like one obvious way to do that is to bring humans into the equation. And so we see data labeling startups doing really well. We have a concept of annotation cues in Langsmith to bring people in there. And so that actual, like, actual human judgment is a big part of it.

And this is humans annotating the actual trace. So, like, oh, the agent did this and this and this, and that was good or bad?

Yeah, yeah. And sometimes giving, like, natural language feedback on it, like, this is good, this is bad. Should have done this. Sometimes just, like, correcting it, like actual, like, laying out what the correct steps were. Kind of depends on the use case. And it's probably different for model companies doing RL than it is for agent companies building agents, but it's bringing that human judgment to it. But then another thing we see is trying to build proxies for this human judgment. And this is where LLM as a judge type things come in where you can run an LLM or something else that has some semblance of human judgment in it to grade the thing that requires human judgment. And so one of the things that we think a lot about is how to make building these llama judges easy, because a big part of them is making sure that they're aligned with your human judgment and human preferences, because if they're not, then your grader's just bad. And so we have a concept in Langsmith called align evals, where a human goes in, labels some traces, and then that builds an LLM as a judge that kind of is calibrated against those traces, because a big part of it is bringing this human judgment. And you just want to make sure that if you're bringing a proxy of it, it's well calibrated.

Interesting. I remember when we first got into business with you, we were emailing about LLM as judge. Is it a viable idea or not? So it seems like it's come a long way.

Okay, so there's a few different aspects of LLM as a judge. Right. There's like, the immediate. So what most people use them for in evals is taking this trace and give it a score of 1 to 0 or 0 to 10 or something like that. And, yeah, I think that's viable. And people are doing that. They're doing it offline. They're also doing it online. Because some of these judgments you don't need truth for. But I think the other area where this comes into is. I mean, you kind of see this in the coding agents themselves. Like, the coding agents will. They'll work up and tell something. Then they hit an error, and they get an error, and then they have to correct there. And so they're kind of judging their previous work. And we Also see this in memory. Like a big part of memory is like reflecting on traces and then updating something. And so can LLMs reflect on traces that are either like their own or their own from a previous session or someone? Yeah, absolutely. I think they can. We see this all across evals and just like error correcting and memory, it's all kind of the same thing.

I see. And then maybe. Okay, so you have all this. You have all the traces.

Yep.

You have the evals.

Yep.

I think the natural question that comes to mind for me is, is the eval a reward signal for reinforcement learning or is it a feedback mechanism for, you know, human engineers to improve the.

Harness or for agent engineers to improve the harness? Because everyone's. No one's. No one's coding manual anymore. They're all using these. So, yeah, one big thing that we've seen is like, we. We have a Langsmith MCP and we have Langsmith Fetch, which is a cli, because coding agents are actually great at using clis. You give that to an agent and it can pull down traces and diagnose what went wrong, and then. And then it brings those traces into the code base where it can then fix it. That's absolutely a pattern that we are seeing and we really, really, really want to support that pattern.

Oh, that's crazy.

Yeah, I know.

And it's good.

Yeah, yeah, yeah, yeah, it's good. Like it. Yeah. And so we see. I'm probably more bullish on that than on kind of like reinforcement learning, at least for like the agent app, kind of like companies right now.

That seems like real recursive self improvement, though.

Yeah. I think again, there's still human in the loop. So like, back to the point around, like, things are good when you can do something as a first draft, like, it. It changes the prompt and then the human reviews it and like, it keeps it on the rails. But like, I. Absolutely. So. So one of the things we launched was Langsmith Agent Builder, which is a no code way to build agents. One of the cool things that we have in there is memory. And so right now, the way that memory works is when you interact with an agent. So it's not in the background yet. It's not like pulling down its traces. But when you interact with the agent, if you say, oh, you should instead of X, you should have done. Yeah, it will go to its own instructions, which are just files, and it will edit those files. So then in the future. And so that's also kind of like a version of this one thing we do want to add is like the thing that runs every night, looks at all the traces for the day, updates its own instructions.

The dreaming thing.

Yeah, yeah. Sleep time compute.

Sleep time compute, is that what it's called?

That's a term, yeah. I think LEDA came up with that. It's a great term. Yeah, that is good.

Awesome. Okay, let's talk more about the future. What are you most excited about? It sounds like you're talking a lot about memory here.

I like memory a bunch. Yeah. I mean I think asking the agents to improve themselves is, I mean I think very, very cool and can be useful in a lot of situations. Not useful in all situations by the way, like if I'm chatting. So ChatGPT added memory. I don't actually really use that feature that much and I don't think it's created any more stickiness for me to use the product or anything like that. And I think part of the reason is when I go to ChatGPT I do like everything's a one off thing. Like I don't really repeat myself that much. I'm asking about software, I'm asking about food trips, like everything in Agent Builder you build kind of like specific workflows for specific things. So I have an email agent and.

I actually, I know it's been emailing me for two years.

Well, so, okay, so I had an email agent outside of Agent Builder and it had this memory as part of it. We then built Agent Builder and I wanted to move it into. Didn't have all of my memories and that was a big. Even though it had the same starter prompt and the same tools. And that was actually, I still haven't fully switched over because it kind of sucks now compared to what it was before, like compared to the other one. And if I just interact with it then it will get better and it will stop sucking. But like that's where memory I think can be like a real mote. And I absolutely think that we're at a point right now where LLMs can look at traces and change things about their code. And I think the question then becomes how do you do that in a way that's safe and acceptable to users? But I think that's absolutely something that we'll see more of for specific scenarios. Not all of them. I still don't know if this would be useful in GPT in this form at least.

How do you think the UI around working with Long Horizon agents will evolve?

I think there probably needs to be like a sync mode and an async mode. So Long Horizon agents running for a long time, probably default, would be some sort of like, async way to manage them. Like, you're. If it runs for like a day, you're not just going to sit there and wait for it to finish. You're probably going to kick off another one and another one and do a bunch of work. And so I think this is where like, async management of things comes into play. I think things like Linear and Jira and Kanban boards and maybe even email are interesting to look at for inspiration about, like, what it looks to like to basically manage a lot of these agents. But I think for a lot of these, at some point you're going to want to switch into synchronous communication with these agents because they come back with a research report and you want to give it feedback that it wrote something wrong. And I actually think chat's like, reasonably good at that. The only thing that I'll maybe say there is that so many of these agents are now modifying other things like files in a file system, that having some way to view that state is really important. And so you see this in coding, where IDEs are still used when you want to go in and manually kind of like change code. And even when I kick off CLAUDE code, when it finishes, sometimes I pull it up and look at the code that it actually wrote. And so I think having a way to view that state is interesting. One of the really cool things that Anthropic did with their CLAUDE cowork launch, when you set it up, you choose the directory that it's kind of like working in, and you're basically saying this is your environment. And obviously that's what you do in coding as well. You open your ID to a particular directory. But I think that's a nice mental kind of framing is like, this is your workspace. That workspace could be a Google Drive, it could be a notion page, it could be anything that stores state. And then you and the agent are collaborating on that state. You kick it off, you manage maybe a bunch of these running asynchronously, then you go into sync mode where you chat with it, but you also view the state. And so that's kind of what I see right now.

And this is like your agent inbox idea then, of, you know, to enable the sync mode, your agent's gonna have to need a way of reaching you.

Yeah, exactly. And yeah, so the agent Inbox or something, we launched that about a year ago and had this idea of like, ambient agents that ran in the background and pinged. And the first version of that didn't have a sync mode. And so it would ping you and then you'd give a response, but then you kind of just wait for it to ping you again. But oftentimes, like when I was switching in to email you and respond to you, I would say very small things and I didn't want to switch out and wait. Like you're really important. So I wanted to like be in the sync mode in this conversation with the agent. And so one of the things we added was this was now when you open the inbox, you're brought into chat and chat is very synchronous and that was actually a big unlock. So I actually think having just in async mode, I don't think that really works right now. Maybe in the future if they get so good that you don't really need to like correct them as much, it gets more viable. But at least right now I think we see people switching from async to sync and back and forth.

What do you think of code sandboxes? Like, is every agent going to have access to a sandbox? Is every agent going to have access to or a computer? Is every agent going to have access to a browser?

Really good question. Something we're thinking a bunch about. I think coding has clearly worked more than browser use so far. So at least in the short term, it seems like if any of those are going to be a key part there, it's going to be this code execution part. File systems. I'm completely file system pilled. I think in some form agents should have access to some file system coding. I may be not as pilled, but I'm probably maybe 90% there. Yeah, I think it is definitely possible there are. It's maybe for like the longer tail of use cases. So maybe there's something where if you're doing something repeated, you need code less. But I think file systems are still useful because that repeated thing could be generating a lot of context and you need to do context engineering. But for the long tail of things, coding's great and there's really no replacement for that browser use. I think the models just aren't good enough right now. From what we've seen, you could probably give like a coding agent, a CLI to do browser use. And there's probably some approximation there. There's probably some people doing some. I think I have seen some cool stuff there. And then computer use is like a weird hybrid of the two. So if, yeah, code sandboxes I really like code sandboxes.

Yeah. Cool. Harrison, thank you so much for joining us today. You have consistently seen the future on agents, and it was really cool to have this conversation and talk about how context engineering has evolved to the current point in time with harnesses and long horizon agents. And so thank you for driving that future and thank you for always chatting with us about it.

Thank you for having me on. I look forward to being back on sometime in the future and being completely wrong about everything I said today. So it's very hard to predict the future. Sam.