setup

cli-dispatch setup

cli-dispatch is a multi-backend delegation hub. Five worker backends are available:

Follow these steps:

1. Detect which worker CLIs are available so you can recommend a sensible default:

   command -v claude >/dev/null 2>&1 && echo "claude: found" || echo "claude: MISSING"
   command -v agy    >/dev/null 2>&1 && echo "agy: found ($(agy --version 2>/dev/null))" || echo "agy: MISSING"
   command -v codex  >/dev/null 2>&1 && echo "codex: found ($(codex --version 2>/dev/null))" || echo "codex: MISSING"
   command -v opencode >/dev/null 2>&1 && echo "opencode: found ($(opencode --version 2>/dev/null))" || echo "opencode: MISSING"
   command -v copilot >/dev/null 2>&1 && echo "copilot: found ($(copilot --version 2>/dev/null))" || echo "copilot: MISSING"
   

2. Ask the user which backend(s) to install with AskUserQuestion (header: "Backends", multiSelect). Offer: DeepSeek, Antigravity (Gemini), Codex (OpenAI), OpenCode (OpenRouter), GitHub Copilot. In the option descriptions, note which underlying CLI each needs and whether it was found in step 1 (e.g. if codex is MISSING, say it can be installed after). For OpenCode, note it needs an OpenRouter API key (paste-yourself, no OAuth) and that if opencode was MISSING in step 1, it can be installed after. For Copilot, note it needs an active GitHub Copilot subscription plus gh auth login or COPILOT_GITHUB_TOKEN/GH_TOKEN. Map the (possibly multiple) answers to a comma-list: DeepSeek→deepseek, Antigravity→antigravity, Codex→codex, OpenCode→opencode, Copilot→copilot (e.g. all five → deepseek,antigravity,codex,opencode,copilot, also accepted as all).

3. Cross-reference step 2's picks against step 1's detection, and offer to auto-install any missing CLI(s):

   • Map each backend chosen in step 2 to the underlying CLI step 1 checked: DeepSeek→claude, Antigravity→agy, Codex→codex, OpenCode→opencode, Copilot→copilot. Determine which of the chosen backends' CLIs came back MISSING in step 1.
   • If none are missing, skip this step entirely and run the installer in step 4 exactly as today, with no new flag.
   • If one or more are missing, ask a separate AskUserQuestion (header: "Auto-install?") that explicitly names each missing CLI and the exact command(s) that would run for it:
     • claude → npm i -g @anthropic-ai/claude-code (fallback: curl -fsSL https://claude.ai/install.sh | bash)
     • agy → curl -fsSL https://antigravity.google/cli/install.sh | bash
     • codex → npm i -g @openai/codex (fallbacks: brew install --cask codex, or curl -fsSL https://chatgpt.com/codex/install.sh | sh)
     • opencode → npm i -g opencode-ai
     • copilot → npm i -g @github/copilot (fallbacks: brew install --cask copilot-cli, or curl -fsSL https://gh.io/copilot-install | bash) In the question text, state plainly that the agy installer and the curl-based fallbacks for claude/codex/copilot download and execute a script from the vendor's domain (antigravity.google, claude.ai, chatgpt.com, gh.io) — the user should know this before approving. Offer:
     • "Yes, auto-install" — the installer will be invoked with --install-missing (bash) / -InstallMissing (PowerShell) in step 4, so it attempts each missing CLI via package manager or vendor script, falling back to the existing MISSING warning if that fails.
     • "No, I'll install manually" — proceed exactly as today, no new flag; the user installs the missing CLI(s) themselves whenever they like. Leave neither option marked recommended: true — running a vendor's install script is a deliberate, per-user tradeoff, not something to nudge them toward.
   • This approval is per-run only: always ask again in a fresh setup run, even if the user approved auto-install previously — never treat a prior session's answer as standing consent.