20260601
This commit is contained in:
34
concepts/agent-harness-engineering.md
Normal file
34
concepts/agent-harness-engineering.md
Normal file
@@ -0,0 +1,34 @@
|
||||
---
|
||||
title: "Agent Harness Engineering(Agent 执行骨架工程)"
|
||||
created: 2026-05-23
|
||||
updated: 2026-05-23
|
||||
type: concept
|
||||
tags: [agent, infrastructure, harness, production]
|
||||
sources: [raw/papers/agent-harness-engineering-survey-2026.md]
|
||||
confidence: high
|
||||
---
|
||||
|
||||
# Agent Harness Engineering
|
||||
|
||||
> Agent Harness 是包裹 LLM 的基础设施层,负责管理长时间、多步骤任务执行的执行环境、工具接入、上下文、编排、可观测性、验证和治理。
|
||||
|
||||
## 核心定义
|
||||
|
||||
Agent Harness 不是 Agent 框架(开发工具),也不是 Agent 平台(产品 SaaS),而是**使 Agent 可靠运行的底层控制平面**。它将执行、工具、上下文、编排、可观测性、验证和治理七个维度统一为一个工程表面。
|
||||
|
||||
## 为什么 Harness 比模型更关键?
|
||||
|
||||
- Bölük (2026a):仅改变 harness 格式就能同时提升 15 个 LLM 的编程能力
|
||||
- Anthropic (2026a):基础设施设置可测量地改变 benchmark 分数
|
||||
- 生产部署中,失败更多源自 harness 配置错误而非模型推理错误
|
||||
|
||||
## 相关概念
|
||||
|
||||
- [[etclovg-taxonomy]] — 七层分类体系
|
||||
- [[binding-constraint-thesis]] — 约束瓶颈论
|
||||
- [[prompt-to-harness-evolution]] — 三阶段工程演进
|
||||
- [[harness-coupling-problem]] — 跨层耦合问题
|
||||
|
||||
## 参考论文
|
||||
|
||||
[[agent-harness-engineering-survey]]
|
||||
Reference in New Issue
Block a user