Install AI coding tools
Install and sign in to a supported AI coding tool so Multica can execute runs on your machine.
A local runtime has two parts: the Multica daemon, and one AI coding tool it can invoke. Install only the tool you intend to use — you do not need all of them.
Choose a tool
A tool that is already installed and signed in needs no extra setup. Tools differ in models, MCP, session resumption, and skill support; the details are in AI coding tools comparison.
Multica currently detects these commands:
| Tool | Detected command | Official install guide |
|---|---|---|
| Antigravity CLI | agy | Antigravity install and sign-in |
| Claude Code | claude | Claude Code quickstart |
| CodeBuddy Code | codebuddy | CodeBuddy quickstart |
| CodeArts | codearts | CodeArts CLI quickstart |
| Codex CLI | codex | Codex CLI |
| GitHub Copilot CLI | copilot | Install Copilot CLI |
| Cursor Agent | cursor-agent | Install Cursor CLI |
| DeepSeek Harness | dsh | DeepSeek Harness |
| DevEco Code | deveco | DevEco Code |
| Grok Build | grok | Grok Build quickstart |
| Hermes Agent | hermes | Hermes quickstart |
| Kimi CLI | kimi | Kimi CLI |
| Kiro CLI | kiro-cli | Install Kiro CLI |
| MiniMax Code | mcode | Install MiniMax Code CLI |
| Muse Code | muse | Install Muse Code |
| OpenClaw | openclaw | Install OpenClaw |
| OpenCode | opencode | OpenCode quickstart |
| Pi coding agent | pi | Pi coding agent |
| Oh-My-Pi | omp | Oh-My-Pi install |
| Qoder CLI | qodercli | Qoder CLI quickstart |
| Qoder CN CLI | qoderclicn | Qoder CN CLI quickstart |
| Qwen Code | qwen | Qwen Code |
| QwenPaw | qwenpaw | QwenPaw |
| Reasonix | reasonix | Reasonix |
| TRAE CLI | traecli | TRAE official site |
| Dim | dim | DimCode |
| Devin CLI | devin | Install Devin CLI |
| ZeroClaw | zeroclaw | ZeroClaw quickstart |
"Supported" means Multica can invoke that CLI. It does not mean Multica provides the tool's account, subscription, or model quota for you.
Sign in on your machine
After installing, launch the tool once in a terminal on its own and complete its sign-in or model provider setup. If the tool cannot complete requests in the terminal, the daemon's invocations fail the same way.
Those login credentials are stored locally by the tool itself. Multica never receives login tokens from Claude, Codex, Cursor, or any other CLI.
Below the minimum version, the daemon does not register the corresponding runtime:
| Tool | Minimum version |
|---|---|
| Antigravity | 1.1.10 |
| Claude Code | 2.0.0 |
| Codex | 0.100.0 |
| Copilot | 1.0.0 |
| Grok | 0.2.89 |
| Qwen Code | 0.20.0 |
| MiniMax Code | 0.1.2 |
| OpenCode | 1.1.54 |
| Dim | 0.3.10 |
| Devin CLI | 3000.3.22 |
| ZeroClaw | 0.8.0 |
A few tools need extra setup beyond signing in:
Confirm the daemon can find the command
Replace <command> with a command from the table, such as claude, codex, or cursor-agent. The first command prints the executable path.
On macOS, Linux, or WSL:
command -v <command>
<command> --versionIf the terminal finds the tool but Desktop or the background daemon does not, the two are usually using different PATH values. Restart the app, or set an absolute path through the matching MULTICA_<PROVIDER>_PATH environment variable; full configuration is in Environment variables.
Re-detect and confirm the runtime is online
Start the daemon:
multica daemon startIf the daemon is already running, restart it after installing a new tool:
multica daemon restartThen open Multica's Runtimes page. The tool appears under the target computer and shows as online. You can now select this runtime when creating or editing an agent.
The daemon must detect at least one built-in supported CLI before it will start. Custom runtime profiles sync after the daemon is up, so they cannot be the sole startup condition on a blank machine. There is one exception: when the daemon has just begun installing the DSH runtime profile itself (MULTICA_DSH_PROFILE_BUNDLE), it starts with no runtimes and registers DeepSeek Harness once that install finishes. Without it, a host whose only tool is a DSH that needs the profile could never complete the install — the daemon would exit before it finished and take it down with it.
No tools detected
Check in order:
- Run the tool itself in a terminal to confirm installation and sign-in are complete.
- Check the actual command name and path with
command -vorGet-Command. - Run
multica daemon logs -fand look for version, path, or authentication errors. - Restart the daemon so it re-reads the current environment.
- Return to the Runtimes page and confirm the computer and the tool are online.
If the tool shows as online but runs still fail, open the issue's run record to see the exact error the CLI returned, or continue with Troubleshooting.
Next steps
- Create and configure an agent — select the runtime you just connected.
- Daemon and runtimes — online status, concurrency, and custom runtimes.
- AI coding tools comparison — compare what each tool can do in Multica.