Auto-sync: 2026-04-26 00:02
This commit is contained in:
28
wiki/concepts/Memory-Based-Handoff.md
Normal file
28
wiki/concepts/Memory-Based-Handoff.md
Normal file
@@ -0,0 +1,28 @@
|
||||
---
|
||||
title: "Memory-Based Handoff"
|
||||
type: concept
|
||||
tags: [multi-agent, memory, handoff, workflow]
|
||||
last_updated: 2026-04-26
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
一种多 Agent 协作中的交接模式,通过外部记忆服务器(而非人工复制粘贴)实现 Agent 间的上下文传递。当一个 Agent 完成工作时,将交付物存储到共享记忆服务器;下一个 Agent 通过 recall 操作自动检索所需上下文,无需人工干预。
|
||||
|
||||
## Core Mechanism
|
||||
|
||||
1. **存储(remember)**:Agent 完成任务后,将交付物快照存入记忆服务器,带上项目标签(如 `retroboard`)和接收方标签(如 `frontend-developer`)
|
||||
2. **召回(recall)**:下一个 Agent 激活时,通过 recall 操作按标签检索历史记忆,自动获取上一个 Agent 的交付物
|
||||
3. **无需人工粘贴**:人类不再充当"粘合剂",记忆服务器接管上下文传递
|
||||
|
||||
## Aliases
|
||||
- Memory-Based Handoff
|
||||
- MCP Memory Handoff
|
||||
|
||||
## Related Patterns
|
||||
|
||||
- [[Sequential Handoff]]:前身模式——必须人工复制粘贴完整输出,Memory-Based Handoff 将其升级为自动召回
|
||||
- [[Memory-Based Handoff]] ← enabled_by ← [[MCP Memory Server]]
|
||||
|
||||
## Source
|
||||
- [[workflow-with-memory]]:完整工作流文档,包含 4 周 MVP 场景下的 Memory-Based Handoff 实践
|
||||
Reference in New Issue
Block a user