Back to Details

agent-collaboration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Agent Collaboration

Agent协作

Choose the smallest route that provides the fresh judgment, parallelism, or durable observation the user requested. A skill defines the workflow; the selected backend owns execution.
选择能够满足用户所需的全新判断、并行处理或持续观测需求的最简路径。Skill定义工作流；选定的后端负责执行。

Route the work

任务路由

  1. Direct work is the default when the task does not benefit from an independent judgment or concurrent lane.
  2. One focused delegate uses the host's native one-off delegation when available. When the user requests Grok, invoke 
    grok-subagent
    ; do not duplicate its CLI and central-review procedure here. If the current agent is already Grok, work directly unless a fresh isolated judgment is material.
  3. Pi subagents fit two or more independent read-only lanes or a scout-worker-fresh-reviewer loop. Use this route only when Pi's 
    subagent
    tool is available. Otherwise recommend it without pretending to execute it.
  4. Herdr is a top-level session control surface. Control it only when the user explicitly asks for Herdr, then invoke the 
    herdr
    skill. A Herdr-hosted Pi session may own Pi children; Herdr observes that lifecycle rather than becoming a second child orchestrator.
If the preferred backend is unavailable, state that constraint and use the smallest available route that preserves the requested independence. Ask before switching to a materially different model, service, repository, or execution scope.
  1. 直接工作：当任务无法从独立判断或并发执行路径中获益时，默认采用此方式。
  2. 单一专注委托：若宿主支持原生一次性委托，则使用该方式。当用户要求使用Grok时，调用
    grok-subagent
    ；请勿在此处重复其CLI和集中审核流程。如果当前Agent已是Grok，除非需要全新的独立判断，否则直接开展工作。
  3. Pi子代理：适用于两个或更多独立只读执行路径，或“侦察员-执行者-全新审核员”循环。仅当Pi的
    subagent
    工具可用时才使用此路径。若不可用，可推荐该方式，但请勿假装执行。
  4. Herdr：是顶级会话控制界面。仅当用户明确要求使用Herdr时才对其进行控制，随后调用
    herdr
    Skill。由Herdr托管的Pi会话可拥有Pi子代理；Herdr仅观测其生命周期，而非成为二级子代理编排器。
若首选后端不可用，需说明该限制条件，并采用能够保留所需独立性的可用最简路径。在切换至差异显著的模型、服务、仓库或执行范围前，需先征得用户同意。

Preserve ownership

保留所有权

  • Keep exactly one writer in a working tree. Put parallel writers in isolated worktrees created before delegation.
  • Give scouts and reviewers fresh context and read-only authority. A single writer may inherit or fork the approved plan when that context is useful.
  • Start a fresh mutation agent instead of reusing a bloated long-lived session.
  • Give every delegate one bounded outcome, relevant paths, existing changes to preserve, exact verification, and a stopping condition.
  • Keep nested delegation off unless the task defines a bounded fan-out and one parent remains responsible for synthesis.
  • For analysis, review, or planning requests, keep every delegate read-only.
The top-level owner independently reads the final diff, runs the required checks, resolves conflicting reports, and owns commit, push, publication, and other external effects unless the user explicitly assigns them elsewhere.
  • 在工作树中仅保留一个写入者。将并行写入者置于委托前创建的独立工作树中。
  • 为侦察员和审核员提供全新上下文及只读权限。当该上下文有用时，单一写入者可继承或复刻已获批的方案。
  • 启动全新的变更Agent，而非复用臃肿的长会话。
  • 为每个委托方设定明确的成果边界、相关路径、需保留的现有变更、精确验证要求以及停止条件。
  • 禁用嵌套委托，除非任务明确限定了扩展范围，且有一个父代理负责成果合成。
  • 对于分析、审核或规划请求，确保所有委托方均为只读权限。
顶级所有者需独立查看最终差异、执行必要检查、解决冲突报告，并负责提交（commit）、推送（push）、发布及其他外部操作，除非用户明确将这些职责分配给其他方。

Complete the collaboration

完成协作

Report which route ran, which agents received mutation authority, how isolation was enforced, what evidence the owner verified directly, and any work that still requires user or runtime validation. Completion requires the owner to account for every changed file and every failed or missing lane.
需汇报执行的路径、获得变更权限的Agent、隔离机制的实施方式、所有者直接验证的证据，以及仍需用户或运行时验证的工作内容。完成协作要求所有者对所有已变更文件以及每个失败或缺失的执行路径负责。