Update nexus: fix conflicts and sync local changes
This commit is contained in:
@@ -1,63 +1,63 @@
|
||||
---
|
||||
title: "Private Context"
|
||||
type: concept
|
||||
tags: [OpenClaw, Agent, Architecture, Memory]
|
||||
sources: [multi-agent-team]
|
||||
last_updated: 2026-04-23
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**Private Context** 是多 Agent 系统中,每个 Agent 独立维护的会话历史和领域特定笔记,与 Shared Memory 共同构成 Agent 的完整知识体系。
|
||||
|
||||
## 核心洞察
|
||||
|
||||
> "Shared memory + private context: The combination is critical — agents need common ground (goals, decisions) but also their own space to accumulate domain expertise"
|
||||
|
||||
私有上下文的作用:
|
||||
- **积累领域专长**:Agent 在独立空间深耕专业知识
|
||||
- **会话连续性**:Agent 能记住自己的历史决策和上下文
|
||||
- **避免干扰**:专业笔记不会与其他 Agent 混淆
|
||||
|
||||
## 私有上下文结构
|
||||
|
||||
```
|
||||
team/agents/
|
||||
├── milo/ # Milo 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 战略分析和笔记
|
||||
├── josh/ # Josh 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 商业分析和模型
|
||||
├── marketing/ # 营销 Agent 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 营销研究和趋势分析
|
||||
└── dev/ # 开发 Agent 的私有上下文
|
||||
├── sessions/ # 会话历史
|
||||
└── notes/ # 技术笔记和技术债追踪
|
||||
```
|
||||
|
||||
## 与 Shared Memory 的关系
|
||||
|
||||
**Private Context** + **Shared Memory** 组合是关键:
|
||||
|
||||
| 维度 | Shared Memory | Private Context |
|
||||
|------|---------------|-----------------|
|
||||
| **可见性** | 所有 Agent | 仅该 Agent |
|
||||
| **用途** | 团队协调、共同决策 | 领域深耕、专业积累 |
|
||||
| **更新频率** | 决策时更新 | 持续积累 |
|
||||
| **典型内容** | 目标、决策、状态 | 会话历史、专业笔记 |
|
||||
|
||||
## 为什么两者都需要
|
||||
|
||||
- **只有共享记忆**:Agent 缺乏领域深度
|
||||
- **只有私有上下文**:Agent 无法协调,形成知识孤岛
|
||||
- **两者结合**:既能有团队协作,又能深耕专业
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Shared Memory Architecture]] — 团队共享记忆
|
||||
- [[Agent-Memory]] — OpenClaw 的长期记忆机制
|
||||
- [[Agent Specialization]] — 专业化 Agent 依赖私有上下文积累深度
|
||||
- [[OpenClaw]] — workspace 目录体系支持私有上下文
|
||||
|
||||
---
|
||||
title: "Private Context"
|
||||
type: concept
|
||||
tags: [OpenClaw, Agent, Architecture, Memory]
|
||||
sources: [multi-agent-team]
|
||||
last_updated: 2026-04-23
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**Private Context** 是多 Agent 系统中,每个 Agent 独立维护的会话历史和领域特定笔记,与 Shared Memory 共同构成 Agent 的完整知识体系。
|
||||
|
||||
## 核心洞察
|
||||
|
||||
> "Shared memory + private context: The combination is critical — agents need common ground (goals, decisions) but also their own space to accumulate domain expertise"
|
||||
|
||||
私有上下文的作用:
|
||||
- **积累领域专长**:Agent 在独立空间深耕专业知识
|
||||
- **会话连续性**:Agent 能记住自己的历史决策和上下文
|
||||
- **避免干扰**:专业笔记不会与其他 Agent 混淆
|
||||
|
||||
## 私有上下文结构
|
||||
|
||||
```
|
||||
team/agents/
|
||||
├── milo/ # Milo 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 战略分析和笔记
|
||||
├── josh/ # Josh 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 商业分析和模型
|
||||
├── marketing/ # 营销 Agent 的私有上下文
|
||||
│ ├── sessions/ # 会话历史
|
||||
│ └── notes/ # 营销研究和趋势分析
|
||||
└── dev/ # 开发 Agent 的私有上下文
|
||||
├── sessions/ # 会话历史
|
||||
└── notes/ # 技术笔记和技术债追踪
|
||||
```
|
||||
|
||||
## 与 Shared Memory 的关系
|
||||
|
||||
**Private Context** + **Shared Memory** 组合是关键:
|
||||
|
||||
| 维度 | Shared Memory | Private Context |
|
||||
|------|---------------|-----------------|
|
||||
| **可见性** | 所有 Agent | 仅该 Agent |
|
||||
| **用途** | 团队协调、共同决策 | 领域深耕、专业积累 |
|
||||
| **更新频率** | 决策时更新 | 持续积累 |
|
||||
| **典型内容** | 目标、决策、状态 | 会话历史、专业笔记 |
|
||||
|
||||
## 为什么两者都需要
|
||||
|
||||
- **只有共享记忆**:Agent 缺乏领域深度
|
||||
- **只有私有上下文**:Agent 无法协调,形成知识孤岛
|
||||
- **两者结合**:既能有团队协作,又能深耕专业
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Shared Memory Architecture]] — 团队共享记忆
|
||||
- [[Agent-Memory]] — OpenClaw 的长期记忆机制
|
||||
- [[Agent Specialization]] — 专业化 Agent 依赖私有上下文积累深度
|
||||
- [[OpenClaw]] — workspace 目录体系支持私有上下文
|
||||
|
||||
|
||||
Reference in New Issue
Block a user