写作
Agent 工程
筛选文章 Agent 工程
Agent 工程
第 8 页 · 11 / 95-
jcode：把 Coding Agent 的瓶颈从模型转到 Harness 介绍 jcode 如何把多 Agent 的资源、状态同步和验证放到 Harness 层，说明并行 Coding Agent 的瓶颈不只是模型能力。
-
OpenAI 研究组织跑到 3.1 Agent 工作日后，Builder 的瓶颈开始转移 OpenAI 的组织级数据说明 Coding Agent 使用规模上升后，瓶颈会转向任务拆分、并发调度、Harness、Eval 和结果选择。
-
OpenAI agent workdays and shifting builder bottlenecks OpenAI organization-level data suggests that more coding-agent use shifts bottlenecks to task decomposition, concurrency, harnesses, evaluation, and selection.
-
Agent demos are easy. The harness is the hard part Strands harness-sdk, Harness MCP Server, and HydraFusion show why agent engineering needs control over context, permissions, state, validation, and recovery.
-
Agent Demo 不难，难的是 Harness 从 Strands harness-sdk、Harness MCP Server 和 HydraFusion 看 Agent 工程为什么从模型调用转向上下文、权限、状态、验证与恢复控制。
-
AI Engineering Harness: verifiable delivery for AI code A multi-agent engineering workflow uses isolated worktrees, CI, cold-start review, evidence gates, and layered context to control delivery of AI-generated code.
-
AI Engineering Harness：把 AI 代码放进可验证的工程闭环 介绍一个多 Agent 工程工作流，如何用独立 worktree、CI、冷启动审查、证据门和分层上下文控制 AI 生成代码的交付。
-
Vercel Eve Agent Framework A source-backed review of Vercel Eve’s filesystem-first agent model, durable execution, tools, sandboxes, approvals, deployment, and Vercel platform tradeoffs.
-
Loop Engineering Harness: controlling agent iterations Break down planning, execution, evaluation, state management, and stopping rules to keep multi-step agent tasks controlled and traceable.
-
Loop Engineering Harness：怎样控制 Agent 的迭代循环 把 Harness 作为一种工程模式，拆解计划、执行、评估、状态管理和终止判断，说明 Agent 多轮任务怎样保持可控和可追溯。
-
Building WishLive: A Multi-Agent Runtime A 48-hour hackathon build of an event-driven multi-agent runtime with registry, workflow, execution, negotiation, settlement, and observability layers.