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

General rules

• 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)

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"

   .

gate-cli

What to install (two parts)

1. gate-cli

   — Gate CLI for CEX, info, news, config, and diagnostics. Install using this skill’s

   setup.sh

   (see below).
2. gate-skills — Agent skills from https://github.com/gate/gate-skills. Use your client’s normal skills workflow (

   npx skills add …

   or copy into the per-client skills directory).

1. Install

gate-cli

(

setup.sh

)

skills/gate-cli-installer/setup.sh

gate/gate-cli

gate-cli

# From the gate-skills (or gate-github-skills) repo root
bash skills/gate-cli-installer/setup.sh

# Optional: pin a release tag
bash skills/gate-cli-installer/setup.sh --version v0.6.0

gate-cli

• setup.sh

  installs to

  ${HOME}/.local/bin/gate-cli

  first. If

  ~/.local/bin

  is not already on your

  PATH

  , the script prints a reminder to add:
  

  export PATH="$HOME/.local/bin:$PATH"

  
  Put that in

  ~/.zshrc

  ,

  ~/.bashrc

  , or your shell profile, then restart the terminal or

  source

  the file.
• If

  ~/.local/bin

  cannot be written, the script falls back to

  /usr/local/bin

  (typically already on

  PATH

  on macOS/Linux).
• Older installs may leave

  ${HOME}/.openclaw/skills/bin/gate-cli

  ; agents must still resolve

  gate-cli

  using Which `gate-cli` runs above — do not assume only one directory.

command -v gate-cli
gate-cli --version

2. Install gate-skills (per client)

~/.cursor/skills/

npx skills add https://github.com/gate/gate-skills

~/.claude/skills/

~/.codex/skills/

~/.openclaw/skills/

npx clawhub@latest add https://github.com/gate/gate-skills

gate-cli

3. API keys and errors →

gate-cli config init

• When

  gate-cli

  returns auth or configuration errors (missing key, invalid secret, 401, etc.), guide the user to run

  gate-cli config init

  interactively. That wizard sets the API key and secret in the CLI config (do not ask users to paste secrets into chat).
• For creating keys in the browser: Gate API key management.
• Optional:

  gate-cli config set api-key ...

  /

  config set api-secret ...

  if the user prefers non-interactive config (still avoid echoing secrets in chat).
• For a broader check:

  gate-cli doctor

  .

4. Legacy MCP (optional)

gate-cli migrate --dry-run
# Then when satisfied:
gate-cli migrate --apply

gate-cli

5. Supersedes (naming / docs)

setup.sh

gate-cli config init