20260601
This commit is contained in:
42
concepts/standard-agent-handoffs.md
Normal file
42
concepts/standard-agent-handoffs.md
Normal file
@@ -0,0 +1,42 @@
|
||||
---
|
||||
title: "Standard Agent Handoffs(标准化 Agent 交接)"
|
||||
created: 2026-05-23
|
||||
updated: 2026-05-23
|
||||
type: concept
|
||||
tags: [agent, protocol, handoff, multi-agent, mcp, a2a]
|
||||
sources: [raw/papers/agent-harness-engineering-survey-2026.md]
|
||||
confidence: medium
|
||||
---
|
||||
|
||||
# Standard Agent Handoffs
|
||||
|
||||
> 当 Planner 交给 Executor、Agent 调用 Tool、子 Agent 交还控制、或系统升级到人类时,交接应传递**意图、约束、权限、产物、溯源、预算状态、风险级别、踪迹历史**和**未解决的决策**——而不仅仅是文本摘要。
|
||||
|
||||
## 现有局部标准
|
||||
|
||||
- **MCP**:标准化工具访问(Model Context Protocol, 2025b)
|
||||
- **A2A**:面向 Agent 间通信(A2A Project, 2025)
|
||||
- **OpenTelemetry**:通用追踪基底
|
||||
|
||||
## 缺失的:跨层交接合约
|
||||
|
||||
所需交接协议需要**足够丰富以支持安全和恢复**,但**足够简单以广泛采用**。应明确:
|
||||
|
||||
- 谁授权了该操作
|
||||
- 转移了什么状态
|
||||
- 什么证据支持当前计划
|
||||
- 接收方允许做什么
|
||||
- 何时必须将控制权交还给另一个 Agent 或人类
|
||||
|
||||
## 双重视角
|
||||
|
||||
- **OpenAI Symphony**:将问题追踪器和仓库作为 Agent 工作的控制平面
|
||||
- **Anthropic**:持久进度产物和清晰交接状态
|
||||
- **治理角度**:Agent 身份、委托、权限清单和可审计性在 Agent 代表用户跨系统行动之前是必需的
|
||||
|
||||
## 相关概念
|
||||
|
||||
- [[lifecycle-orchestration]] — 编排中的交接
|
||||
- [[governance-security]] — 交接中的权限转移
|
||||
- [[tool-interface]] — 工具级交接标准
|
||||
- [[agent-harness-engineering-survey]]
|
||||
Reference in New Issue
Block a user