Keep Kilo Code.
Give it your machines.

AI Commander is not an alternative to Kilo Code, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, or Amp. It is the remote-machine harness those tools plug into over MCP: outbound-only shell, detached jobs that outlive the chat, and file transfer on hardware you already own.

Quick start:
  1. Install the host agent on the machine you want your AI to control. It shows a private machine code.
  2. Connect your AI: paste this prompt, then replace AIC-… with your code — Help me connect this AI client to AI Commander using https://aicommander.dev/start.md. Then check the status of my machine: AIC-… — or add the connector URL https://aicommander.dev/mcp and sign in with an email code (per-client steps).
Positioning in one line: Kilo Code stays the brain; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

Sibling harness pages: Cursor · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Kilo Code (MCP URL)

Kilo Code (MCP docs) is an open-source coding agent for VS Code, JetBrains, and CLI with first-class local and remote MCP servers. Point it at AI Commander’s hosted MCP endpoint:

Settings → MCP Servers → Remote (HTTP)
URL: https://aicommander.dev/mcp

Or persist under the top-level mcp key in global (~/.config/kilo/kilo.jsonc) or project (./kilo.jsonc / ./.kilo/kilo.jsonc) config:

kilo.jsonc — mcp
"mcp": { "aicommander": { "type": "remote", "url": "https://aicommander.dev/mcp", "enabled": true } }

Optional Bearer header for account aliases (Kilo supports {env:VARIABLE_NAME} substitution):

headers (optional)
"headers": { "Authorization": "Bearer {env:AICOMMANDER_KEY}" }

Full client matrix (Kilo Code, Amp, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, OpenCode, Qwen Code, goose, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Kilo Code MCP docs: Using MCP in Kilo Code.

First connect may open a one-time browser sign-in (OAuth). For a code-only first hour without that flow, append ?anonymous=1 to the MCP URL. You can disable OAuth on the server entry with "oauth": false if you prefer header-only auth.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Kilo Codemcp.aicommander.url → https://aicommander.dev/mcp
Ampamp mcp add aicommander https://aicommander.dev/mcp
goosegoose session --with-streamable-http-extension "https://aicommander.dev/mcp"
Qwen Codeqwen mcp add --transport http aicommander https://aicommander.dev/mcp
OpenCodeopencode mcp add aicommander --url https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursornpx @aicommander/mcp stdio bridge → remote exec + jobs
Grok / Geminigrok mcp add --transport http … / gemini mcp add
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL
Continue / Windsurfstdio bridge in Continue / Windsurf MCP config

How Kilo Code handles MCP servers

Checked against Kilo Code docs: Using MCP in Kilo Code in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Kilo Code

Kilo has both an editor extension and a CLI, and they share one config. That makes it a practical way to drive the same fleet from your laptop editor and from a terminal session on another box.

  1. Add aicommander to the global ~/.config/kilo/kilo.jsonc as a remote server and finish the OAuth sign-in when the status shows needs_auth.
  2. Allow the read-only tools by key (aicommander_list_machines, aicommander_session_status, aicommander_remote_job_status, aicommander_remote_job_logs) and leave aicommander_remote_exec and aicommander_remote_job_start on ask, because both run commands.
  3. Have Kilo start the long step with remote_job_start and check on it later, from the CLI or the editor.

Limits and gotchas in Kilo Code

FAQ

Is AI Commander an alternative to Kilo Code?
No. AI Commander is a remote-machine harness. You keep Kilo Code (or Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp) as the AI. AI Commander gives those tools secure remote shell, detached jobs, and file transfer on machines you own — over MCP or REST.
How do I connect Kilo Code to AI Commander?
Add AI Commander as a remote MCP server in Kilo Code. In Settings → Agent Behaviour → MCP Servers, add a Remote (HTTP) server with URL https://aicommander.dev/mcp. Or edit kilo.jsonc under the top-level mcp key: { "aicommander": { "type": "remote", "url": "https://aicommander.dev/mcp", "enabled": true } } in ~/.config/kilo/kilo.jsonc (global) or ./kilo.jsonc / ./.kilo/kilo.jsonc (project). First connect may open a one-time browser sign-in (OAuth). Use ?anonymous=1 for a code-only first hour. Optional: set headers Authorization: Bearer <your-key> for account aliases. See /howto/ for the full matrix.
How is this different from Kilo Code running locally only?
Local Kilo Code is the brain in your editor or CLI. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Kilo Code can run shell, detached jobs, and file transfer on those machines over MCP.
Why does Kilo Code give up on long AI Commander commands?
Kilo's default MCP timeout is about 15 seconds for remote servers. Set a larger timeout (in milliseconds) on the aicommander entry, or start long work with remote_job_start.
How do I auto-approve only the read-only AI Commander tools in Kilo Code?
Add permission rules for the {server}_{tool} keys, such as aicommander_list_machines and aicommander_remote_job_status, and keep aicommander_remote_exec and aicommander_remote_job_start on ask.

Next steps

Install the agent on a machine you control, connect Kilo Code via MCP URL to https://aicommander.dev/mcp, then ask for a real task on a remote box.