68 lines
2.2 KiB
Markdown
68 lines
2.2 KiB
Markdown
---
|
||
title: "Single Control Plane"
|
||
type: concept
|
||
tags: [OpenClaw, Agent, Architecture, Interface]
|
||
sources: [multi-agent-team]
|
||
last_updated: 2026-04-23
|
||
---
|
||
|
||
## Definition
|
||
|
||
**Single Control Plane** 是多 Agent 系统中，通过单一消息接口（如 Telegram 分组）统一接入所有 Agent，每个 Agent 仅在收到特定标签时响应的架构设计。
|
||
|
||
## 核心洞察
|
||
|
||
> "Single control plane: All agents are accessible through one Telegram group chat — tag the agent you need"
|
||
|
||
单一控制平面的价值：
|
||
- **降低使用门槛**：用户只需在一个地方与团队互动
|
||
- **统一入口**：不需要记住多个 Agent 的独立接口
|
||
- **自然协作**：像在团队群组中与不同成员对话
|
||
|
||
## Telegram 路由配置
|
||
|
||
```
|
||
Telegram group: "Team"
|
||
|
||
Routing:
|
||
- @milo → Strategy agent (spawns/resumes milo session)
|
||
- @josh → Business agent (spawns/resumes josh session)
|
||
- @marketing → Marketing agent (spawns/resumes marketing session)
|
||
- @dev → Dev agent (spawns/resumes dev session)
|
||
- @all → Broadcast to all agents
|
||
- No tag → Milo (team lead) handles by default
|
||
|
||
Each agent:
|
||
1. Reads shared GOALS.md and PROJECT_STATUS.md for context
|
||
2. Reads its own private notes
|
||
3. Processes the message
|
||
4. Responds in Telegram
|
||
5. Updates shared files if the response involves a decision or status change
|
||
```
|
||
|
||
## Agent 处理流程
|
||
|
||
每个 Agent 收到消息时的标准处理流程：
|
||
|
||
1. **读取共享上下文**：GOALS.md 和 PROJECT_STATUS.md
|
||
2. **读取私有笔记**：自己的 agents/<name>/ 目录
|
||
3. **处理消息**：结合上下文和专业知识
|
||
4. **响应 Telegram**：在群组中回复
|
||
5. **更新共享文件**：如有决策或状态变更
|
||
|
||
## 与其他接口模式的对比
|
||
|
||
| 模式 | 描述 | 适用场景 |
|
||
|------|------|----------|
|
||
| **Single Control Plane** | 统一入口 + 标签路由 | 团队协作、多 Agent 协调 |
|
||
| **独立接口** | 每个 Agent 独立通道 | 简单任务、专业工具 |
|
||
| **网页界面** | Web UI 控制台 | 监控和管理 |
|
||
|
||
## Related Concepts
|
||
|
||
- [[OpenClaw]] — 提供 sessions_spawn/sessions_send 能力
|
||
- [[Telegram]] — 常用作控制平面的消息平台
|
||
- [[Multi-Agent Coordination]] — 协调多 Agent 的机制
|
||
- [[Agent Specialization]] — 专业化 Agent 便于标签路由
|
||
|