coordinate-agents：本地双代理协作

Coordinate multiple AI coding agents through a local-first, recoverable Agent Bus.

Two coding agents. One local workspace. Quick start · Features · How it works · Documentation · Changelog English · 简体中文 Overview A local Web Workspace for working with coding agents in two persistent terminals. Use the default Codex + Antigravity pair to delegate implementation and review results, or choose Custom Terminals to bring your own CLI pair. Your projects, task history, terminal sessions, and collaboration receipts stay on your machine. Each agent uses its own CLI configuration and provider login. Coming from v2.4? v3 focuses the npm product on Web Workspace. Find the original v2.4.0 docs and migration guide for the old workflow and version-specific commands. Quick Start Install Node.js >=18 and Git, plus the agent CLIs you want to use. For Default Collaboration, make sure codex and agy work and are signed in before creating a task. Coordinate Agents does not install the agent CLIs. Workspace settings allow choosing Antigravity tool permission mode. The adapter defaults to automatic approval via --dangerously-skip-permissions; choose prompt mode to require tool approval. Explicit saved arguments override the default. npx @hogancv/coordinate-agents@latest web --root "/path/to/project" --port 3000 Open the printed localhost URL, check Workspace settings, and create a task. Choose Default Collaboration, then enter your request directly in Codex. Codex sends the implementation requirements to the paired Antigravity, waits for its receipt, reviews the changes, and reports back to you. Use --port 0 to choose a free port. The startup folder is registered automatically; if it is not already a Git repository, startup initializes Git and local Workspace storage without creating a commit. A Codex Plugin is not needed. Published npm package and current source The 3.0.2 Web release includes the features added after 3.0.1: Git Changes and review feedback, Custom Terminals, desktop notifications, Collaboration Timeline/Health, and native Codex conversation recovery. Use @3.0.2 for a pinned install, or verify npm dist-tags.latest before using @latest. The source checkout remains available for development; merging to main does not publish npm. git clone https://github.com/hogancv/coordinate-agents.git cd coordinate-agents npm ci node bin/coordinate-agents.mjs web --root "/path/to/project" --port 3000 If you already have a checkout, run npm ci and the last command from its root. See Getting started for the first-task walkthrough and Troubleshooting for startup problems. What you can do Capability How it works in the current source Default Collaboration Codex clarifies, delegates, and reviews; Antigravity implements. Each task starts a fresh terminal pair. Custom Terminals Choose two installed CLI executables, including the same CLI twice, with optional shared and per-terminal prompts. Multiple projects Browse local folders, switch projects without closing background sessions, and search project/task history. Persistent terminals Type directly, resize, focus one terminal, use Zen mode, and reconnect after page refresh. Close or restart sessions explicitly. Reopen the original Codex conversation Supported local Codex CLI 0.163.x automatically saves the native conversation binding. Reopen task uses the saved UUID; Recover executor preserves a live Codex and rebuilds the missing executor. Completed terminal startup makes the task ready without an extra UUID confirmation. Action table and fallback. Git Changes and review feedback Inspect working-tree changes, select diff lines, and send review notes to the task's Codex after confirming its input is ready. Collaboration Timeline Browse persisted dispatch and agent-report events by round. Collaboration Health See missing progress receipts and session problems, with a configurable attention threshold. Desktop notifications Opt into DONE, APPROVED, and FAILED receipt notifications on Windows 10/11 or macOS. Local history Archive tasks or projects; clear archived conversations explicitly from settings. Bilingual interface Switch between Simplified Chinese and English. The Workspace guide explains settings, prompts, feedback, notifications, storage, and session lifecycle. How default collaboration works You enter a request in Codex → Codex sends requirements to this task's Antigravity → Antigravity reports WORKING, implements, then reports DONE or FAILED → Codex reviews the diff and validation → Codex reports APPROVED, or requests changes in a new round The supplied workspace-message.mjs helper binds messages to the selected task and terminal pair. It records explicit cooperation reports; ordinary terminal output and idle do not prove that work is complete. SENT confirms input dispatch only. DONE means the agent reports implementation ready for review. APPROVED is Codex's reported review decision, not independent verification. Workspace task status describes terminal lifecycle, not implementation or review completion. Collaboration prompts guide agent behavior; they are not an enforced workflow state machine. Timeline and health views observe recorded facts and do not automatically dispatch, retry, restart, or review work. Each Web task uses the selected project's working directory. A new terminal pair does not create an isolated Git worktree, so avoid conflicting edits across tasks. Custom Terminals Choose Custom Terminals when you want to control the two agents and their instructions yourself. Commands must be executable names or absolute paths, without inline arguments or shell syntax. Configure project defaults in settings; each task snapshots its commands and optional prompts, including for restarts. Shared prompts are limited to 8 KB UTF-8 and per-terminal prompts to 4 KB. Preview or copy them, or explicitly send after checking that the target CLI is ready for multiline bracketed paste. Custom mode supplies no built-in Planner/Implementer roles, collaboration rounds, or Send to Codex feedback. Git diff viewing and copying remain available. Local dat