Kolleague Docs

Install AI coding tools

Install and sign in to a supported AI coding tool so Kolleague can execute tasks on your machine.

A local runtime has two parts: the Kolleague daemon, and one AI coding tool it can invoke. Install only the tool you intend to use — you do not need all of them.

1. 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.

Kolleague currently detects these commands:

ToolDetected commandOfficial install guide
Antigravity CLIagyAntigravity install and sign-in
Claude CodeclaudeClaude Code quickstart
CodeBuddy CodecodebuddyCodeBuddy quickstart
Codex CLIcodexCodex CLI
GitHub Copilot CLIcopilotInstall Copilot CLI
Cursor Agentcursor-agentInstall Cursor CLI
DevEco CodedevecoDevEco Code
Grok BuildgrokGrok Build quickstart
Hermes AgenthermesHermes quickstart
Kimi CLIkimiKimi CLI
Kiro CLIkiro-cliInstall Kiro CLI
OpenClawopenclawInstall OpenClaw
OpenCodeopencodeOpenCode quickstart
Pi coding agentpiPi coding agent
Qoder CLIqodercliQoder CLI quickstart
Qoder CN CLIqoderclicnQoder CN CLI quickstart
Qwen CodeqwenQwen Code
TRAE CLItraecliTRAE official site

"Supported" means Kolleague can invoke that CLI. It does not mean Kolleague provides the tool's account, subscription, or model quota for you.

2. 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. Kolleague never receives login tokens from Claude, Codex, Cursor, or any other CLI.

Claude Code requires 2.0.0 or later, Codex 0.100.0 or later, Copilot 1.0.0 or later, Grok 0.2.89 or later, and Qwen Code 0.20.0 or later. Below the minimum version, the daemon does not register the corresponding runtime.

3. Confirm the daemon can find the command

On macOS, Linux, or WSL, run:

command -v <command>
<command> --version

In Windows PowerShell, run:

Get-Command <command>
<command> --version

Replace <command> with a command from the table, such as claude, codex, or cursor-agent. The first command prints the executable path.

If 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 KOLLEAGUE_<PROVIDER>_PATH environment variable.

4. Re-detect and confirm the runtime is online

Start the daemon with the CLI:

kolleague daemon start

If the daemon is already running, restart it after installing a new tool:

kolleague daemon restart

With Kolleague Desktop, quit and reopen the app.

Then open Kolleague'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.

No tools detected

Check in order:

  1. Run the tool itself in a terminal to confirm installation and sign-in are complete.
  2. Check the actual command name and path with command -v or Get-Command.
  3. Run kolleague daemon logs -f and look for version, path, or authentication errors.
  4. Restart the daemon so it re-reads the current environment.
  5. 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

On this page

1. Choose a tool2. Sign in on your machine3. Confirm the daemon can find the command4. Re-detect and confirm the runtime is onlineNo tools detectedNext steps