https://dextermayhewjd.github.io/projects/learn-claude-code/s13/Recent content in S13 Agent Teams：让多个 Agent 协作 on dextermayhewjdHugozh-cnhttps://dextermayhewjd.github.io/projects/learn-claude-code/s13/01-team-messaging/Mon, 01 Jan 0001 00:00:00 +0000https://dextermayhewjd.github.io/projects/learn-claude-code/s13/01-team-messaging/<div class="chapter-outline" id="s13-messaging-outline" aria-labelledby="s13-messaging-outline-title"> <p class="chapter-outline__title" id="s13-messaging-outline-title">本节目录</p> <nav id="TableOfContents"> <ul> <li><a href="#message-storage">1. 消息在模型上下文之外暂存</a> <ul> <li><a href="#message-position">1.1 独立历史，共享邮箱总线</a></li> <li><a href="#message-diagram">1.2 本地最小流程</a></li> <li><a href="#message-fields">1.3 消息字段与几种不同用途</a></li> </ul> </li> <li><a href="#message-implementation">2. MessageBus 内部怎样收发</a> <ul> <li><a href="#message-path">2.1 初始化与路径检查</a></li> <li><a href="#message-send">2.2 send：追加一行并通知等待者</a></li> <li><a href="#message-read">2.3 read：消费所有消息</a></li> <li><a href="#message-wait">2.4 wait：等待到消息或超时</a></li> </ul> </li> <li><a href="#message-delivery">3. 模型何时看到这些消息</a> <ul> <li><a href="#message-context">3.1 队友与 Lead 的消费边界不同</a></li> <li><a href="#message-assignment">3.2 普通消息不等于任务重新分配</a></li> </ul> </li> </ul> </nav> </div> <p>我想先弄清楚：<strong>消息放在哪里，谁把它读出，怎样变成下一次模型请求的输入？</strong></p>https://dextermayhewjd.github.io/projects/learn-claude-code/s13/02-team-protocols/Mon, 01 Jan 0001 00:00:00 +0000https://dextermayhewjd.github.io/projects/learn-claude-code/s13/02-team-protocols/<div class="chapter-outline" id="s13-protocol-outline" aria-labelledby="s13-protocol-outline-title"> <p class="chapter-outline__title" id="s13-protocol-outline-title">本节目录</p> <nav id="TableOfContents"> <ul> <li><a href="#protocol-position">1. 协议不是把“批准了”写进聊天</a> <ul> <li><a href="#protocol-state">1.1 request_id 与执行闸门</a></li> <li><a href="#protocol-diagram">1.2 计划协议的局部流程</a></li> </ul> </li> <li><a href="#protocol-plan">2. 计划：请求、审批、应用分别由谁做</a> <ul> <li><a href="#protocol-submit">2.1 队友提交时保存当前工作身份</a></li> <li><a href="#protocol-review">2.2 Lead review_plan 处理请求</a></li> <li><a href="#protocol-apply">2.3 队友校验回复才更新本地闸门</a></li> <li><a href="#protocol-gate">2.4 真正限制执行的位置</a></li> </ul> </li> <li><a href="#protocol-shutdown">3. 关机：另一条请求与响应协议</a> <ul> <li><a href="#protocol-stop-request">3.1 Lead 请求，队友在收信边界确认</a></li> <li><a href="#protocol-stop-response">3.2 Lead 消费响应并结束请求状态</a></li> </ul> </li> </ul> </nav> </div> <p>普通消息只表达意思；<strong>协作协议还要匹配请求、改变状态，并限制实际执行。</strong></p>https://dextermayhewjd.github.io/projects/learn-claude-code/s13/03-task-claiming/Mon, 01 Jan 0001 00:00:00 +0000https://dextermayhewjd.github.io/projects/learn-claude-code/s13/03-task-claiming/<div class="chapter-outline" id="s13-claim-outline" aria-labelledby="s13-claim-outline-title"> <p class="chapter-outline__title" id="s13-claim-outline-title">本节目录</p> <nav id="TableOfContents"> <ul> <li><a href="#claim-position">1. 沿用 S10 的依赖图，增加共享执行约束</a> <ul> <li><a href="#claim-dependencies">1.1 先建节点，后连依赖，再认领</a></li> <li><a href="#claim-diagram">1.2 候选发现与最终认领的局部流程</a></li> </ul> </li> <li><a href="#claim-functions">2. 发现、认领、完成各负责什么</a> <ul> <li><a href="#claim-scan">2.1 scan_unclaimed_tasks：找候选</a></li> <li><a href="#claim-next">2.2 claim_next_task：尝试当前仍可用的任务</a></li> <li><a href="#claim-atomic">2.3 claim_task：锁内验证并绑定 owner / cwd</a></li> <li><a href="#claim-complete">2.4 complete_task：只有当前 owner 能完成</a></li> <li><a href="#claim-release">2.5 两种释放：正常回合结束与异常退出</a></li> </ul> </li> <li><a href="#claim-storage">3. 锁与文件：与邮箱的保证不同</a> <ul> <li><a href="#claim-lock">3.1 task_store_lock：线程锁加文件锁</a></li> <li><a href="#claim-save">3.2 save_task：完整替换单个任务文件</a></li> <li><a href="#claim-loop">3.3 从 IDLE 接回工作循环</a></li> </ul> </li> </ul> </nav> </div> <p><strong>任务板保存可执行工作，扫描发现候选，锁内认领决定归属。</strong> 队友等待时可以接手 ready task；不是依赖另一轮 LLM 调度。</p>https://dextermayhewjd.github.io/projects/learn-claude-code/s13/04-worktree-isolation/Mon, 01 Jan 0001 00:00:00 +0000https://dextermayhewjd.github.io/projects/learn-claude-code/s13/04-worktree-isolation/<div class="chapter-outline" id="s13-worktree-outline" aria-labelledby="s13-worktree-outline-title"> <p class="chapter-outline__title" id="s13-worktree-outline-title">本节目录</p> <nav id="TableOfContents"> <ul> <li><a href="#worktree-position">1. Worktree 属于任务，不是另一个 Agent</a> <ul> <li><a href="#worktree-layout">1.1 目录、分支与任务之间的关系</a></li> <li><a href="#worktree-order">1.2 正确的调用顺序</a></li> <li><a href="#worktree-diagram">1.3 从任务绑定到工具 cwd 的局部流程</a></li> </ul> </li> <li><a href="#worktree-functions">2. 创建、解析与具体工具入口</a> <ul> <li><a href="#worktree-create">2.1 create_worktree：验证后创建，再绑定</a></li> <li><a href="#worktree-resolve">2.2 task_worktree_cwd：校验绑定仍真实有效</a></li> <li><a href="#worktree-assignment">2.3 assignment_cwd：归属与目录必须一致</a></li> <li><a href="#worktree-tool">2.4 队友文件工具是具体包装，不是全局 chdir</a></li> </ul> </li> <li><a href="#worktree-lifecycle">3. 什么时候能移除</a> <ul> <li><a href="#worktree-remove">3.1 remove_worktree 是宿主操作</a></li> <li><a href="#worktree-summary">3.2 完成任务、结束回合、清理目录是三件事</a></li> </ul> </li> </ul> </nav> </div> <p>独立 Agent 上下文隔离了推理历史；<strong>可选 worktree 再把不同任务的文件修改放到不同 Git 工作目录。</strong></p>