Ona’s customer-controlled execution model will allow agents to operate inside an organization’s own cloud environment while OpenAI provides the intelligence and orchestration that power the experience.
这句话划出了一条关键的架构分界线："智能与编排"由 OpenAI 提供，"执行环境的控制权"留在客户自己的云里。这正是 EP.97 专题01 架构图里"安全网关/本体"层要解决的问题——企业愿意把工作交给 Agent 云端持续执行的前提，是自己仍然掌握基础设施、数据和安全边界。
We believe people should be able to delegate more ambitious work without remaining tied to the machine where it began.
这句话几乎就是 EP.97 专题01 提出的"设备解耦"设计公理的官方原话版本——OpenAI 明确把"任务不再绑定发起它的那台设备"当作 Codex 下一阶段的核心设计目标，而收购 Ona 正是为了补齐这一目标所需的持久化云端执行基础设施。
the need to specify goals, constraints, context, and evaluation did not disappear
Lilian Weng 用 prompt engineering 的历史类比预测 harness 工程的走向：手工技巧会被模型能力提升逐渐内化，但"目标/约束/上下文/评估该如何被清晰表达"这个需求本身不会消失，只会转移到更高的抽象层。这是判断 Agent 设计下一步会往哪走的一条重要经验规律，也支撑了 EP.97 专题01 对"完整形态"的预测：接口会更简单，但背后的工程复杂度不会归零。
the system surrounding a base model that orchestrates execution and decides how the model thinks and plans, calls tools and acts, perceives and manages context, stores artifacts, and evaluates results.
这是"harness"这个概念在本篇最精确的定义——不是模型本身，而是包裹模型的执行系统。EP.97 专题01（Cowork Agent 完整形态）的架构图直接建立在这个定义上：设备解耦、检查点可恢复、多端可观测这些设计公理，本质上都是在给"harness 层"而不是"模型层"做工程。
no single architecture dominates; rather, effectiveness depends on aligning the memory structure with the specific workload bottleneck
对智能体记忆系统的批判性审视。当前业界没有一刀切的完美架构，记忆模块的设计必须与具体的任务瓶颈相匹配。这打破了“通用记忆系统”的幻想，提示我们在构建 Agent 时需要针对局部维护成本和任务特征进行定制化设计。
why Devin separates the "brain" from the machine , why repo setup is still one of the hardest problems , why Docker is not always enough, and how full VMs, snapshots, scoped secrets, GitHub bots, Slack integrations, and video-based testing all fit together.
The 'brain from the machine' separation is a non-obvious architectural decision — it means the AI model runs separately from the environment it's operating in, enabling proper permission scoping and security boundaries. The list of required infrastructure (VMs, snapshots, scoped secrets, video testing) reveals that building an async agent product is far more of a DevOps challenge than an AI challenge.
Agents address the problem from independent angles, other agents try to refute what they found, and the run keeps iterating until the answers converge—which is how a workflow reaches results a single pass can't.
Convergence through adversarial iteration is borrowed from ensemble methods and scientific peer review — but applied to code. The non-obvious implication: this architecture is more robust to the hallucination problem than single-pass generation, because refuting agents are specifically incentivized to find failures. It's a form of AI quality control built into the workflow itself.
Meta also explicitly highlighted parallel multi-agent inference as a way to improve performance at similar latency
令人惊讶的是，Meta明确强调了并行多代理推理作为在相似延迟下提高性能的方法。这表明AI系统正在从单一模型向多代理系统演进，可能是解决复杂问题的新范式，同时也暗示了未来AI系统架构的重大转变。
see that progress had been made, and declare the job done
这是大语言模型常见的“过度乐观”陷阱。模型倾向于迎合用户的完成预期，而非客观审视实际进度。通过强制读取结构化的feature list，是用外部状态锚定来对抗模型的内在偏见。
Rather than treating a complex document as a single monolithic task, Deep Extract deploys sub-agents to break it down and conquer each piece, which is what allows it to remain accurate even on documents with thousands of rows across hundreds of pages.
大多数人可能认为处理复杂文档的最佳方式是将其作为一个整体来处理，保持上下文完整性。但作者提出将复杂文档分解为多个子任务并由子代理分别处理的方法更有效，这一方法挑战了文档处理中'整体优于部分'的传统认知，暗示分解策略可能更适合处理超长文档。