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.
- Install the host agent on the machine you want your AI to control. It shows a private machine code.
- 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 URLhttps://aicommander.dev/mcpand sign in with an email code (per-client steps).
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:
Or persist under the top-level mcp key in global
(~/.config/kilo/kilo.jsonc) or project
(./kilo.jsonc / ./.kilo/kilo.jsonc) config:
Optional Bearer header for account aliases (Kilo supports {env:VARIABLE_NAME} substitution):
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 |
How Kilo Code handles MCP servers
- Current Kilo builds configure servers under a top-level
mcpkey inkilo.jsonc. The global file is~/.config/kilo/kilo.jsonc; a project can usekilo.jsoncor.kilo/kilo.jsonc. The VS Code extension and the CLI read the same files. - Each server is
"type": "local", withcommandas an array and anenvironmentmap, or"type": "remote", with aurland optionalheaders. - Remote servers try Streamable HTTP first and fall back to SSE.
- OAuth is automatic for remote servers. If the server needs a sign-in, its status shows
needs_auth. Set"oauth": falsewhen you authenticate with a header instead. - Timeouts are in milliseconds. The defaults are short: about 10 s for local servers and 15 s for remote ones.
- Tool permissions use
{server}_{tool}keys, for exampleaicommander_list_machines, with allow/ask/deny values. Choosing "Approve Always" in the permission dock writes that rule for you.
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.
- Add
aicommanderto the global~/.config/kilo/kilo.jsoncas a remote server and finish the OAuth sign-in when the status showsneeds_auth. - Allow the read-only tools by key (
aicommander_list_machines,aicommander_session_status,aicommander_remote_job_status,aicommander_remote_job_logs) and leaveaicommander_remote_execandaicommander_remote_job_starton ask, because both run commands. - Have Kilo start the long step with
remote_job_startand check on it later, from the CLI or the editor.
Limits and gotchas in Kilo Code
- With a 15-second default timeout, a
remote_execthat runs a build will hit Kilo's timeout before the result comes back. Raisetimeoutor use detached jobs. - Older Kilo docs and blog posts show an
mcpServersblock inmcp_settings.json. Current releases use themcpkey inkilo.jsonc, so check which format your version reads. - Turning MCP off shrinks the system prompt. If the AI Commander tools vanish, check that MCP is still on under Settings → Agent Behaviour → MCP Servers.
FAQ
timeout (in milliseconds) on the aicommander entry, or start long work with remote_job_start.{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.