Now vibe coding, so learning hammer FE ?https://channel.meo-ai.comhttps://channel.meo-ai.com/posts/655https://channel.meo-ai.com/posts/655Tue, 02 Jun 2026 01:36:06 GMT<span class="post-title-source">《如何构建你自己的Agent_Harness：从单体框架到可组合Worker架构》</span><br /><br />标签：<a href="/search/result?q=%23AI%E5%B7%A5%E7%A8%8B" title="#AI工程">#AI工程</a> <a href="/search/result?q=%23Agent%E6%9E%B6%E6%9E%84" title="#Agent架构">#Agent架构</a> <a href="/search/result?q=%23%E7%B3%BB%E7%BB%9F%E8%AE%BE%E8%AE%A1" title="#系统设计">#系统设计</a> <a href="/search/result?q=%23%E5%BC%80%E6%BA%90%E6%A1%86%E6%9E%B6" title="#开源框架">#开源框架</a> <a href="/search/result?q=%23Worker%E6%A8%A1%E5%9E%8B" title="#Worker模型">#Worker模型</a><br /><br />总结：<br />iii创始人Mike_Piccolo提出了一种全新的Agent_Harness构建理念——将传统单体框架拆分为15个独立的可替换Worker，通过统一的<code>iii.trigger()</code>原语和WebSocket协议进行通信。这种架构让团队不再需要Fork或绕过现有框架，而是通过"安装/替换Worker"来精确组装符合自身需求的Agent运行时，实现从极简到企业级的平滑伸缩。<br /><br />文章要点：<br />1. 传统框架的痛点：LangChain、LangGraph等将循环、工具、记忆、编排等打包成单体，团队要么全盘接受，要么Fork或Hack，导致长期运行后不得不重写整个Harness<br />2. iii的核心理念：将15个Harness职责（凭证解析、模型目录、预算追踪、审批门、 durable_turn_loop等）拆分为独立Worker，每个Worker通过<code>iii.trigger()</code>触发，可独立版本化、用任意语言编写、随时替换<br />3. 实际生产栈示例：包括turn_orchestrator（11状态FSM）、approval_gate（审批路由）、llm_budget（预算管控）、hook_fanout（钩子发布）、provider_anthropic/openai/kimi（模型提供商）等11个Worker，全部通过同一引擎总线通信<br />4. 替换的便利性：想换动态模型目录？写一个注册<code>models::list</code>的新Worker即可；想从Slack审批？写一个监听slash命令并调用<code>approval::resolve</code>的Worker；整个堆栈其他部分完全无感知<br />5. 架构优势：单体框架的"薄vs厚"之争在这里变成配置问题——极简Harness只需4个Worker，企业级Harness安装全部13个+自定义策略引擎，距离只是<code>config.yaml</code>的条目增减，而非重写<br />6. 可观测性统一：每个Worker自动注入OpenTelemetry追踪，通过<code>iii.session.id</code>等标签实现跨Worker的完整调用链可视化<br /><br />URL：<a href="https://iii.dev/blog/how-to-build-your-own-agent-harness/" target="_blank" rel="noopener" title="https://iii.dev/blog/how-to-build-your-own-agent-harness/">https://iii.dev/blog/how-to-build-your-own-agent-harness/</a><a class="tgme_widget_message_link_preview" href="https://iii.dev/blog/how-to-build-your-own-agent-harness" target="_blank" rel="noopener" title="Most agent teams adopt a harness as one decision. iii decomposes it into eleven independently-replaceable workers on one engine bus. Build your own stops meaning fork a framework and starts meaning swap a few workers."> <div class="link_preview_site_name accent_color">iii.dev</div> <img class="link_preview_image" alt="How to Build Your Own Agent Harness" src="/static/https://cdn4.telesco.pe/file/mVeyUr3S2yB6PnOO3JSbVxMsAiuIoq3lnhsXB2R9SO55T8SZQ3g4V4FKhnFKmXnie0BgoK60oCoPKg4HLEF_EBVf6RYvDd-GSt85XCZJfkxq-wAfRkScgR0U-lFiBAq9WCC-seQlnoD-O6mudJecIOCLMGB6BTaaVDeNXTrjs3jkLqEy2nIpU5Fq8mk3oDdZUV-LUOaD4P_3To0w9VsKXB6tmCBB4Us2Mlb3VkkNOqLUzAEhuC3zW8AJ_2yteR95fZjhUbnBCP5WLIcD0ZSsKiJhEGN7IOWLX_I0o41tXCoDgLnI1ZNKOzGp9CjedLtv1BUJbvq6O_NbZ_L1gIsuFQ.jpg" width="1200" height="630" loading="eager" /> <div class="link_preview_title">How to Build Your Own Agent Harness</div> <div class="link_preview_description">Most agent teams adopt a harness as one decision. iii decomposes it into eleven independently-replaceable workers on one engine bus. Build your own stops meaning fork a framework and starts meaning swap a few workers.</div> </a>