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.

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

Remote shell on Linux, macOS, and Windows — by session code or saved alias.
Detached jobs for builds, training, and headless agents on the box that has the repo.
Fleet list + GPU facts so Kilo Code picks the right machine before it burns an hour.
File courier (Pro) for checkpoints and diffs up to 100 MiB.

Not a replacement — a multiplier

You already use	AI Commander adds
Kilo Code	`mcp.aicommander.url → https://aicommander.dev/mcp`
Amp	`amp mcp add aicommander https://aicommander.dev/mcp`
goose	`goose session --with-streamable-http-extension "https://aicommander.dev/mcp"`
Qwen Code	`qwen mcp add --transport http aicommander https://aicommander.dev/mcp`
OpenCode	`opencode mcp add aicommander --url https://aicommander.dev/mcp`
Claude Code	`claude mcp add --transport http …` → remote exec + jobs
Codex / ChatGPT	Same MCP endpoint or REST `/api/v1/exec`
Cursor	`npx @aicommander/mcp` stdio bridge → remote exec + jobs
Grok / Gemini	`grok mcp add --transport http …` / `gemini mcp add`
Cline / Roo Code / Zed	MCP settings / `context_servers` + bridge or remote URL
Continue / Windsurf	stdio bridge in Continue / Windsurf MCP config

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.

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.

Install the agent Setup guides Remote coding agents

Keep Kilo Code.Give it your machines.