正在打开每日关注
正在打开每日关注
通过多窗口 Agent 分工、审查与隔离提升研发协作效率。
𝗛𝗲𝗿𝗱𝗿 has been great these past few days. Claude and Codex each get a pane. The main agent assigns work, waits, reads, and follows up. I used to carry every conclusion between windows myself. With ChatGPT, Codex, and other agents, one works and another reviews. 𝗣𝗿𝗼𝗺𝗽𝘁: Run this task with multiple agents in parallel: [TASK] You are the coordinator. Check which agents and panes are available, then split the task only where pieces can move independently. Give each agent one clear outcome. State the deliverable, how it will be checked, what it may change, and what it must not touch. Research and review agents may share the current workspace, but they must stay read-only. For work inside a Git repo, give every agent that edits files its own worktree so no two writers share a checkout. Use Herdr to assign work to the other panes, wait for their results, read their output, and follow up yourself. Do not ask me to relay messages. When different agents are available, have one execute and another review. Swap roles on the next pass if useful. Settle factual disagreements with a test. You decide judgment calls. Bring the work together in one place. For a Git repo, integrate through one checkout and rerun the real checks. Do not push, publish, touch production, or expose secrets without my approval. Finish with the result, verification evidence, unresolved issues, and any panes or worktrees still running.
是什么 这是一条关于 Herdr 多窗口多智能体协作的经验分享,不是具体代码教程。作者描述由主 Agent 负责拆解、派工、等待、读取结果和追问,Claude、Codex 等 Agent 分别在独立 pane 中承担工作;人与 Agent 之间不再靠手工搬运上下文。
核心机制 其工作流接近“协调者—执行者—审查者”:能并行的任务先拆开,研究与评审保持只读,真正修改 Git 仓库的 Agent 使用各自 worktree,最后由协调者汇总并在同一 checkout 中重跑检查。执行与审查可以交替,分歧尽量通过测试解决。
关键洞察 价值不只是同时打开几个窗口,而是把并发条件、权限范围、交付物、验证标准和禁止触碰范围写成明确契约。这样可以降低上下文切换成本,提升代码实现、研究和复核的吞吐,也让 Agent 结果更容易追责和复现。
边界与风险 推文没有交代 Herdr 的具体实现、通信协议、失败重试、状态持久化或成本控制,不能据此推断产品能力。并行任务只有在依赖关系清晰时才适用;共享环境仍可能产生竞态、重复劳动和错误合并。只读约束、worktree 隔离、秘密保护以及最终集成检查,决定了这套方法能否安全落地。