Skip to main content
Open Settings → CLI configuration and pick an engine on the left. The app detects the local binary and offers Install / Update. Clicking those shows a plan first, then runs after you confirm. It will not silently run an install script for you. Credentials, providers, and capability differences live on each engine page. This page covers detect, install entries, and troubleshooting.

Claude Code

Hosted providers, local settings.json, CLI login.

Codex

~/.codex/ and sandbox.

Kimi

~/.kimi-code/config.toml.

Grok

~/.grok/config.toml; use WSL on Windows.

OpenCode

opencode.json; env injection does not change the local file.

Pi

auth.json and /login.

DeepSeek Harness

host / port and Web UI.

Provider overview

How to choose, capability differences, where config is written.
Gemini, Cursor, Copilot, Qwen, and similar items appear under Coming soon. This page does not document install steps for them.

​
Workflow

1

Pick an engine

Open Settings → CLI configuration and open the engine you want to install.
2

Install

Click Install and confirm the plan, or install yourself with the terminal commands on that engine page.
3

Confirm the command works

Open a new terminal and run the matching --version, such as claude --version, codex --version, or kimi --version.
4

Add credentials

Go back to that engine page: local config, a hosted provider, Pi auth.json, or the DSH Web UI.
5

Switch in the input

When status is ready, you can ask a question.

​
What the in-app install preview shows

When you click Install in the app, the preview command depends on the engine: Grok has no npm release. In-app Install for Grok is not available on Windows; run the official script in WSL. OpenCode and DSH have no in-app uninstall, so you do not delete login data or $DSH_HOME by accident. Exact commands are in the Install section on each engine page.

​
When detect fails

  1. Open a new terminal and confirm the binary is on PATH
  2. A GUI opened from a launcher sometimes cannot see your shell PATH. Write it into system environment variables and restart the app
  3. Override a custom CLI path on that engine page
  4. Come back to Settings and detect again
  5. Confirm the engine is not in the Disabled group
  6. For DSH, also confirm the host is up: open http://127.0.0.1:3080 in a browser