coordinate-setup

Coordinate Setup

Use this skill for first-run onboarding. Use the Coordinate Agents MCP tools for normal setup operations; do not generate a shell command for the user. The Plugin bundles the Runtime, but coordinate-agents is not guaranteed to be on PATH.

Normal MCP operations:

coordinate_agents_setup_discover
coordinate_agents_setup_configure

Only if MCP is unavailable, or if the user explicitly requests debugging, let <skill-dir> be the absolute directory containing this loaded SKILL.md and use the bundled fallback. The following shell syntax is not the normal Plugin path:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" ...

For the normal Plugin path, call coordinate_agents_setup_discover with { "root": "<repository>" } before changing configuration. The equivalent fallback/debug invocation is:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" setup --root "<repository>" --json

It checks codex, claude, agy, agy-proxy, and gemini by resolving the actual executable. It reports unavailable commands and distinguishes detected-but-not-configured agents. Detection never writes configuration. The response also includes the additive adapters registry snapshot with each registered identity, Contract version, capabilities, and configured Agent facts. A trusted external adapter is represented without launching it; when an external Agent is already configured, discovery uses only that adapter's Contract-defined detect() operation for availability facts.

When the user chooses an agent, inspect its native help and perform one high-level setup transaction through coordinate_agents_setup_configure. It writes the machine-specific executable to ~/.coordinate-agents/config.json, registers/updates the project Agent, assigns the workflow role, checks executable availability, and returns READY facts. Do not manually compose config set, agent add, workflow editing, and doctor calls:

An explicitly registered external adapter can be selected with its exact identity through the same operation. The returned adapters snapshot is additive and keeps Agent identity, Adapter identity, and executable identity separate. An unavailable or incompatible adapter fails before either the user configuration or project workflow transaction is committed, and the Runtime rolls back any partial setup changes.

Fallback/debug syntax only:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" setup configure \
  --agent antigravity --command agy-proxy --adapter antigravity-cli \
  --role implementer --root "<repository>" --json

For a generic CLI, pass an explicit argument template containing {prompt} after checking that CLI's own --help; otherwise Runtime returns UNSUPPORTED_CAPABILITY rather than claiming that executable detection means adapter compatibility:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" setup configure \
  --agent claude --command claude --adapter generic-cli \
  --args '["--print","{prompt}"]' --role implementer \
  --root "<repository>" --json

User configuration is stored outside the plugin at ~/.coordinate-agents/config.json (Windows: C:\Users\<username>\.coordinate-agents\config.json). An explicit project command in .agent-bus/config.json takes precedence over the user file. Setup configure does not write the selected machine path to project config unless a project override already exists; it refuses to replace an existing explicit project command. Agent identity, Adapter, and executable remain separate, so antigravity may use agy-proxy without falling back to agy.

The selected command is also the persistent Session executable. The Runtime uses structured argument arrays, bounded PTY I/O, and only the configured project root; it does not control a Codex App terminal panel or another desktop window.