正在打开每日关注
正在打开每日关注
通过分工、工作树隔离与只读评审,让多个 CLI Agent 并行协作并由主 Agent 集成验证。
I use 𝗢𝗿𝗰𝗮 a lot too. Herdr handles pane handoffs; Orca tracks CLI agents’ worktrees, tasks and completion. 𝗣𝗿𝗼𝗺𝗽𝘁: Use Orca for [TASK]. One clear goal per worker. Reviewers read only; writers get worktrees. Run in parallel; wait for worker_done. Another agent checks commits. One owner integrates and tests. No push or prod unless approved. Report results, blockers and leftovers.
𝗛𝗲𝗿𝗱𝗿 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.
是什么 这是一套面向 CLI Agent 的并行协作编排提示词与实践反馈。Herdr 被用于在不同 pane 之间分派和接收工作,Orca 用于追踪 Agent 的 worktree、任务与完成状态;主 Agent 负责拆题、调度、追问和汇总。它解决的不是单个代码问题,而是多 Agent 协作中的上下文搬运与责任边界问题。
核心设计 流程将角色和权限显式化:每个 worker 只承担一个清晰目标,研究者和评审者保持只读,写作者获得独立 worktree;只有可独立推进的子任务并行运行,并以 worker_done 作为同步点。另设 Agent 检查提交,由一个 owner 统一集成、测试和报告,push、发布与生产操作保留人工批准闸门。
关键洞察 最值得借鉴的是“并行化执行、集中化决策”:隔离写入面降低互相覆盖,明确交付物和验收方式减少模糊委派,主 Agent 仍保留全局判断权。结果、阻塞项和遗留项的标准化,也便于继续迭代或审计。
边界与风险 文本没有提供实际项目规模、成功率或冲突数据,不能据此证明效率一定提升。worktree 只能隔离文件修改,无法自动解决共享服务、数据库、依赖版本或语义合并冲突;pane 可用性、完成信号和权限控制也依赖宿主工具的真实实现。落地时应保留人工评审与测试门禁。