Agent orchestrators and agent coordinators are not the same layer
说明与用途
将编排器和协调器角色分离,可安全并行运行多个编码代理,防止会话丢失和冲突更改。
问题
Developers using multiple coding agents lack clear separation between orchestration (starting/stopping agents) and coordination (declaring intents and resolving conflicts), leading to lost sessions, conflicting changes, and unclear visibility.
结果
Separating orchestration and coordination allows developers to run multiple coding agents concurrently without losing sessions or creating conflicting changes, improving reliability and visibility.
工作流
- Identify the agents you will run in parallel.
- Deploy an orchestrator (e.g., dmux, agent-deck) to spawn and schedule agent sessions.
- Run Foremerge as a coordinator to publish intents before agents edit code.
- Foremerge compares intents, detects conflicts, and returns findings.
- If conflicts are found, resolve them manually or adjust intents.
- Once all intents are verified, agents proceed with their tasks.
- Monitor the orchestrator’s dashboard to track session status.
- Use Foremerge’s findings to audit changes before merging.
- Iterate the process for subsequent changes.
证据
Foremerge is not an orchestrator. It cannot start an agent, cannot stop one, and does not know when one is running.
An orchestrator’s authority is imperative. It can start things and stop things.
A coordinator never starts or stops anything. Its input is not tasks but declarations.
- 记录日期: 2026-09-19T21:00:17.385Z