gate-cli-installer (Cursor / Claude Code / Codex / OpenClaw)

General rules

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. These rules have the highest priority.
→ Read gate-runtime-rules.md

• Do not document or require legacy Gate MCP server setup in this flow. The supported path is gate-cli + gate-skills.
• If the user previously used Gate MCP, optional cleanup is gate-cli migrate (see Legacy MCP below) — do not let migration block a fresh gate-cli + skills install.

Which gate-cli runs (agents / shells)

Canonical rules (same text as gate-runtime-rules.md §4):

1. Prefer the system binary: If command -v gate-cli resolves to an executable and gate-cli --version succeeds, use that as gate-cli everywhere.
2. User local bin: If step 1 fails, if ${HOME}/.local/bin/gate-cli exists and is executable, gate-cli refers to "${HOME}/.local/bin/gate-cli" for this session (invoke with full path when PATH may be incomplete).
3. OpenClaw skills bin: If steps 1–2 fail, if ${HOME}/.openclaw/skills/bin/gate-cli exists and is executable, gate-cli refers to "${HOME}/.openclaw/skills/bin/gate-cli".