马具与利爪:智能体架构的膨胀律与终极洗牌 AI Engineer 2026-07-21

马具与利爪:智能体架构的膨胀律与终极洗牌

在AI工程实践的演进历程中,行业正在经历从大语言模型(Large Language Model: 基于海量文本训练的 AI 系统)单次调用向复杂智能体系统(Agentic System)的深刻转型。这一光谱的演进不仅是技术栈的叠加,更是开发者对掌控力、鲁棒性以及复杂任务分工的心理诉求的体现。单次大模型调用(Oneshot Call)受限于无状态特征,无法应对现实中具有不确定性的工程任务。为此,行业引入了马具(Harness: 负责封装、调度和约束智能体运行的控制系统),通过提供运行环(Agent Loop)、工具调用、记忆体、失败重试机制以及复杂的上下文工程,为智能体注入了“doggedness(百折不挠的坚韧性)”的工程品质。

在具体实操层面,马具系统从早期的本地控制端(Local Harness)迅速向云端控制端(Cloud Harness)演进。现代马具架构支持了诸多关键特性:通过持久化线程(Thread Persistence)实现连接中断后的无缝恢复;利用会话级工具授权(Session-long Tool Approval)避免频繁交互阻塞;通过命令行(TUI)和斜杠命令(Slash Commands)提供即时的人机交互接口;并能动态生成技能(Skills)以扩展智能体的 Affordance(行为示能)。此外,马具还能在上下文窗口耗尽时进行自动压缩(Autocompact),并调度多线程的并行子智能体(Parallel Sub-agents)来拆解和并发执行任务。这种设计从系统反馈上彻底改变了开发体验,智能体不再仅仅是编辑器的辅助插件,而是能够脱离本地计算资源限制、在云端沙箱(Cloud Sandbox)中自主编译并直接向 GitHub 提交 Pull Request 的高效协作节点。

Original English

I'll get us started. Um, so long day of talks and uh, how are you all feeling? Cool. Yeah, good to see we still have some energy. You know, I know there's a lot of like evening events. Um, we've heard a lot about the present and I'm going to talk about the future. Um, so my talk is called every harness will become a claw. Um, here's a little bit about me. Um, I am the co-founder CEO of Mastra. We are a Typescript agent framework. Um, I am also the author of a book that you may have gotten a copy of either outside or at a previous event. Um, we have seen a lot of agents running in production um, over the last 18 months. And I'm not I'm saying that as kind of context for and stage setting for the thoughts and ideas that I'm about to share right now. Um and uh the thing that I'm going to say is is welcome to the harness era. What do I mean by the harness era? Um well u let's just talk about the types of harnesses that we see right now. We see local harnesses. Um we use them every day daily driving our our coding, right? Um we see cloud harnesses. Um these are both products that we can purchase as well as if we work and some of these uh companies that have built their own internal coding agents that live on Slack. Um and then of course we have the your friendly local uh open source frameworks that have some of these primitives and give you the the tools that you need to build your own. Um and that's where we that's where we fit in. Um now let's talk about where we are sort of collectively as an industry um and how things have evolved over the last we'll say year to to 18 months. Um last year at at AI engineer we were talking a lot about agents. We're talking about the agent loop. We were talking about agents versus workflows. Um so so I want to you know there's as we're thinking about um the agentic spectrum I often compare it to uh self-driving as a spectrum right there are different levels of self-driving autonomy whether that's like lane assist whether that's Tesla S FSD whether that's I I'm sitting in the back of my Whimo and there's nobody behind the steering wheel right um there are various aspects of the agentic spectrum between LLMs agents harnesses and claws and I'm going to talk about what we've seen and where we're going. What makes an agent different than an LM? Hopefully, we mostly know this, but just as a quick refresher, right? It's the agent loop, its tool calls, its memory, it's the ability to retry failed tasks, it's context engineering. Um, Dex is a close friend and an inspiration for this uh one of the inspirations for this talk. Um, and it's agent state, right? These are some things that like hey I'm running an agent in a loop and I can't just do this with a oneshot call uh to to an LLM right I didn't I've tried to make these qualities I don't not sure what the quality of taking actions is active or something so I just put action but um you know qualities here are starting to emerge when we move from an agent to a harness durability and doggedness um a friend of mine was referring to an agent that he was using and he called it dogged which I really like and I'm taking that for this talk, right? So, durability just the sheer quality of like being able to run not for minutes but for hours or days. Um, you know, what what what encompasses this? Well, sometimes it's like, hey, I you know, I uh lost a connection in the middle of the turn and uh you know, but I persisted the stream and so now I can resume from the place where I started, right? There's planning mode. We all see this in cloud code. Um parallel sub aents being able to fan out multiple tasks at the same time. Uh we have more affordances with a TUI and slash commands. We have skills. Um we don't have to define all our agents up front, but we can dynamically create them on the fly. This is, you know, very powerful. Um you can sp the the harness can spin up background bash tasks, right? Um it will autocompact when it runs out of the context window. Uh you know, these are all things we'll see when we use cloud code or codecs, right? Um it persists. it will persist threads, right? You can resume a thread once that's you've like disconnected from later. Um, you can cue, you can steer, you can interrupt. You're not just blocked waiting on the LM. Hey, I take a turn and then you take a turn. I'm playing playing Civilization here and I can't take a turn until all the other civilizations are playing. No, I'm playing Starcraft. I'm playing Age of Empires. And um, right. Uh, you know, session long um tool approval. So it's not just like yeah I approved this specific tool call but yeah you can run all instances of rmrf for slash right that you see in the session even though the first one will probably wipe your machine. Um okay so there there's like you know there's a um there's a few steps here and I'm I'm I'm about halfway through these and then afterwards we're going to talk about what it means and this is kind of a in between step. I think this is something we've seen over the last really 3 months. Um, and I think we're all still starting to grapple with what it means, which is this movement from a local harness to a cloud harness where the harness is always on. What do I mean by a harness that is always on? Well, you might be talking to it in Slack. Maybe you're talking to it in Slack along with your colleagues, right? Um maybe you're each giving it instructions and has to figure out how to parse that and use user metadata. Uh maybe you have a mobile app. I was just uh uh you know maybe you have a mobile app. Maybe it tunnels to your local um to to your local machine. Some of these uh some harness mobile apps do this. Um often like cool. How is this running? Well, it's probably running in a cloud sandbox because it's maybe it's running locally in your machine. and you're tunneling into it, but maybe it's just running in a cloud in the cloud somewhere and it's got a bunch of sandboxes which enables more parallelism. You can get more um parallel sub aents beyond what you can do on your machine. This is always a trade-off and always something you get with distributed systems, right? You can do more in the cloud than you can do locally. You have more resources. It requires a different architecture. It's more powerful. Um and then lastly, you're not creating code, you know, on your just on your local machine or maybe even in a git work tree. um you're you're probably creating, you know, if you're writing code, you're probably creating a PR that that pushes right to to GitHub. Um so so you know, there's a shift, right, from from local harnesses to these always on kind of like cloud harnesses. We're still in the middle of this. You may have you may only be working with a local harness. You may have started to see cloud harnesses pop up in your your organization, right? You may be figuring out how to use them. Your teams may be figuring out how to use them.

Steinberger 定律与“利爪”崛起:主动智能体的设计与自主演进

随着智能体控制系统的不断沉淀,行业开始迈向更加自主的利爪(Claw: 具备完全自主意识、能动性和自优化能力的智能体实体)时代。这一演进趋势可以用所谓的 Steinberger 定律 来概括,即:“任何马具(Harness)都会持续膨胀,直到其演化成利爪(Claw)”。这种技术系统自发性膨胀的底层驱动力,在心理学上源于人类对“多巴胺赌场(Dopamine Casino: 投入低成本的指令/Token,即可高频获取高价值反馈的心理机制)”的渴望。我们希望能在睡前给智能体发送任务,在非同步的交互中享受智能体自动交付成果的多巴胺快感。因此,系统架构必须支持智能体的主动性,使其能够脱离“人机回合制”的束缚。

在实操层面,要构建一个真正的“利爪”系统,必须为其注入主动性(Initiative)与持续学习(Continual Learning)的工程设计:

  • 心跳机制与守护进程:智能体不再是被动等待调用的函数,而是拥有常驻的守护进程(Daemon)和心跳机制(Heartbeat),能够定时苏醒并扫描外部数据源,自主判断是否存在需要响应的紧急事件。
  • 异步多渠道网络:智能体配备了通信网关,能够通过 Slack、WhatsApp、Telegram 等渠道向用户发送主动通知,并处理来自多用户的并发反馈。
  • 基于 Trace 的自我进化:通过分析自身的执行痕迹(Traces),智能体能够自动评估决策质量,甚至在代码层面修改驱动自身的逻辑,或实现技能自动生成(Automatic Skill Generation)以快速适应新环境。

这种设计将系统反馈从“工具使用”拉升到了“自主代理”的维度。智能体通过与云端沙箱和分布式网关的协作,开始展示出自我修正与持续进化的动态生命力。

Original English

Um, and then I want to talk about what the harness to claw transition is, which is imbuing these agents, imbuing these harnesses with initiative and and learning, right? What is initiative? Well, um, if you've used, let's say, a a personal assistant uh, agent, right? And that agent texts you and says, "Hey, I saw an urgent email come in. Is that email actually urgent? Was someone like, you know, spamming you?" you know, but like like the agent is listening um to external feed services. It has a heartbeat which means it wakes up every you know defined amount of time and um and does something right. Uh again like channels some uh you might be able to text it, WhatsApp it, telegram it where whatever you want. Um you you may persist the memory memory in a more accessible later place than just simple sort of like file storage, right? um you you might it might have a a Damon, it might have a a gateway uh for for sending in and receiving incoming outcoming requests. Uh it often will do continual learning, right? So this concept that you know the agent the harness runs and then you know based on the traces that it generates it it sort of autoimproves itself and there's different ways of doing this. you see um skill automatic skill generation for example is a common one. Um it could modify the code driving this as well. Um we haven't figured out what the right way of doing it is yet. We're still exploring you know the industry is still exploring options. Um now the reason that and and maybe this is like our unique vantage point here but you know for the last three months as a framework we've just seen this as a f as the future. And so we furiously looked at the the you know the features that you know openclaw have that Hermes agent have and say and and we've said like look you know a lot of people a lot of folks want these features but they want them with power and control. They don't want to just put a you know a claw on a box right they want to have more. And so, you know, we we've been thinking about this because we we you know, my I'm not doing my job well if I'm not giving everybody the tools that they need to build agents, to build harnesses as with the maximum power, right? Um so, so hopefully like again we hopefully I've walked a little bit through the step transition with actions, durability, doggedness, always on initiative, learning. Again, I I think I failed in like making them all the right tense phrase and making them all qualities, but I hope you get the idea here, right? Um, we're ascending on the agentic spectrum. Um, and what was a simple LLM 18 or 24 months ago is a lot more powerful. So, I've called this without sort of asking consent from Pete, but I've called this Steinberger's law, which is I I believe every harness will expand until it becomes a claw. and and and that's a little bit um technological, that's a little bit economic, that's a little bit psychological. So, let me walk you through the reasoning here. Um the first thing that I've observed um that we've all observed um as a is that harnesses tend to expand. And they expand because we want them to expand. Um we want to DM them in Slack. We want to text them and like start overnight uh tasks before bedtime. We want this dopamine casino that we get when we put in tokens and get out code, right? Um or or whatever other actions, you know, um agent agents are bigger than just coding agents, but um we want our own dopamine casino. And this this image is thanks to uh to Dex Horty. Um but I see something else in our future. um which is that and and it's something that like I don't think we we sort of talk about as much uh but after this after this phase where where we're sort of making everything more and more powerful um there will be a shakeout um and and let me walk you through sort of uh through my reasoning here which is that

终极洗牌:AI 智能体的经济学收敛与开发者的突围策略

随着“马具”持续向“利爪”方向无限膨胀,整个智能体生态正步入一个不可避免的经济学周期——智能体大洗牌(Agent Shakeout: 智能体应用由于用户心智带宽饱和与成本结构制约而发生的行业重塑)。正如2010年代移动互联网爆发时期,iOS 与 Android 平台上涌现了数以万计的应用类型,但人类的大脑心智(Cognitive Bandwidth)是极其有限的。在每个细分赛道中,最终往往只有一到两个绝对领先的标志性产品(如出行赛道的 Uber 与 Lyft)能够留存下来。

根据消费行为学与行业收敛规律,一个成功的智能体应用必须在两个核心维度上占据其一,否则终将被用户遗忘:

  1. 高使用频次(High Frequency):如 DoorDash 或 Uber,用户每天或每周都会频繁发起交互,从而在脑海中建立起强烈的认知通路。
  2. 高经济价值(High Economic Value):如 Airbnb,虽然使用频次较低,但每次交互都解决了一个成本高昂、决策复杂的刚性需求。

如果一个智能体既无法提供高频的多巴胺反馈,又不能解决高价值的痛点问题,它就会像那些毕业后渐行渐远的大学同学一样,从用户的日常工作流中彻底淡出。对于当下的智能体开发者而言,面对AI技术以3至4倍速狂飙突进的现状,核心的突围策略在于:必须紧扣用户的真实痛点来构建差异化能力。开发者不能沉溺于技术的自我狂欢,而要意识到,即使当前爬上了局部的技术山头,也要为 2020 年代后期即将到来的、以格局重塑和市场收敛为特征的第二波行业洗牌做好充足的准备。

Original English

in the 2010s we had these platforms we had Android, we had iOS. And all of a sudden, there were all these things we could do on our phones that we previously weren't able to do. We could get directions, we could hail rides, um, we could send payments. Um, we could play music. Um, other ones emerged over the course of the decade. We could watch short form video. Um, we could [clears throat] watch long form documentaries. We could browse the internet. You know, some were kind of ported over from the desktop. We could browse the internet. Um, again, you know, some, you know, we could order food, right? Um, we could put book accommodations, but but if you look at most of these kinds of categories, and there are quite a few categories, there really only like one or two, you know, logos here that we use, you know, okay, how many maybe, you know, we use Uber and we we use Lyft, but like do anyone use another rideing app here, you know, like and and so when you talk to people that are smart about like consumer behavior, the the reason they say that this is is because you only really have space in your brain for like a limited number of things. Like if if think about something like Thumbtac. So uh Thumbtac didn't really serve a very high economic value. Like Airbnb like we only use it Airbnb occasionally, but when we use it, we like really want it. We really need it. You know, it's really valuable to us. Thumbtac like a little bit less so, right? Um and then it's also like not frequent, right? like maybe maybe like you know something like Door Dash or Uber people can use multiple times a day, right? So there's there's sort of like it either has to be very economically valuable or has to be very frequent. And if it's neither one of the two, um we just forget about it, right? It's like that, you know, college friend that like we haven't really talked to in years. It's not cuz like they weren't important at one point in our life, but like there's just nothing that maybe they moved to a new city or we moved to a new city or our lives, our friend groups, our careers diverged and all of a sudden like, you know, maybe we're calling them once a once a year or once every other year or or whatever. And you know, there's just nothing that makes them pertinent and brings them up in our our brains. And so right now we're like really excited because there's all this energy and excitement and we're all excited to these harnesses that we're like, you know, putting in tokens and getting out like useful things that we all love. Um and and I think that in the notsodistant future there will be this very real shakeout and and these categories will kind of emerge and we'll realize that we only have space in our lives for so many of these claws. They're very powerful. We we love them very much. Um and so I would I would think about um what what what does that mean for you? So the the first thing is um the first thing is don't get this is the reason that like events are are are important that like staying up with like if the rate of change increases 3 to 4x that means you know we need to figure out what's going on even more frequently. That's why we're all here. Um, but if you're building an agent, make sure that it has the capabilities that your users need because if it doesn't and if there's newer things that come out, like they may just, you know, pick pick something that's more powerful because that that's happening very quickly. Um, and then keep in mind that if you if you if you aren't if you're the thing you're working on, um, if even if you climb up to the top of the hill, keep in mind there's going to be another wave of this sort of these like this this shakeout coming. and you know probably sometime in the later 2020s. Uh so um that I'm Sam um I'm the uh I'm the co-founder of Monsterra the the TypeScript agent framework. I'm the author of Principles of Building AI agents. Hopefully you can get a copy of the book outside or I've got a few here. Um please stop by, say hi. Um it's great to see all of you. Thank you all for coming out. It's a real pleasure. Um enjoy the rest of the conference. [music]

📌 文中提及的人物和组织

关键字: agent-framework agentic-workflow industry-trends software-architecture