Skip to main content
Grok, Kimi, OpenCode, and Pi use local binaries. Open Settings → Provider management → CLI. The plugin only checks whether the command exists and what version it is. It does not run install scripts on your computer. Credentials, login, and capability differences live on each engine page. Claude / Codex use SDKs. See those pages.

Claude Code

SDK, API key, local config, and login.

Codex

SDK, ~/.codex/, and sandbox.

Kimi

Local kimi.

Grok

Local grok.

OpenCode

Local opencode.

Pi

Local pi.
CLI detection page The UI copy may mention Gemini, but a standalone runtime is not shipped yet. This page does not include install steps for it.

​
Workflow

1

Install in a system terminal

Open Terminal, iTerm, or PowerShell, and install with the official command on that engine’s page.
2

Confirm the command works

Open a new terminal and run grok --version, kimi --version, opencode --version, or pi --version.
3

Detect in CC GUI

Open Settings → Provider management → CLI and click Detect again.
4

Switch providers in the input box

After the status becomes installed, pick that provider at the bottom of chat and ask a question.
Skip local CLIs if you only want Claude or Codex working first.

​
If detection fails

  1. Open a new terminal and confirm the binary is on PATH
  2. An IDE launched from the Dock / Start menu sometimes cannot read the terminal PATH. Add the install directory to system environment variables, then restart the IDE
  3. Point at the binary with an environment variable: GROK_BIN, KIMI_BIN, OPENCODE_BIN, PI_BIN (also accepts *_PATH / *_CLI_PATH)
  4. Go back to the CLI page and click Detect again
  5. Turn on the related debug switch and check the plugin log