Keep Cline.
Give it your machines.

AI Commander is not an alternative to Cline, Cursor, Claude Code, Codex, ChatGPT, Gemini, Grok, Windsurf, or Continue. 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: Cline 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 · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Cline (MCP settings)

Cline is the popular VS Code / Cursor agent extension. It talks to AI Commander through the same stdio MCP bridge as Cursor and Windsurf. Add this under mcpServers in Cline’s MCP settings (open Cline → MCP Servers, or edit the cline_mcp_settings.json file Cline manages):

cline_mcp_settings.json
{
  "mcpServers": {
    "aicommander": {
      "command": "npx",
      "args": ["-y", "@aicommander/mcp"],
      "env": {
        "AICOMMANDER_SERVER": "https://aicommander.dev"
      }
    }
  }
}

The config shape matches Cursor and other IDE MCP clients; only the settings path differs. Full client matrix (Cline, Cursor, Continue, Windsurf, Claude Code, Codex, ChatGPT, Gemini, Grok, REST): Connect your AI client.

First connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). For a code-only first hour without that flow, append ?anonymous=1 to the MCP URL where your client supports it.

Cline remote control and AI Commander

Two of Cline's documented options for working away from the machine it runs on (checked 2026-10-23): Cline Desktop over SSH runs every session on a remote host: the chat, approvals and live output stay in the app on your computer, while file edits, terminal commands, Git and MCP servers run on the host (Cline docs: Remote Development over SSH). It needs key-based SSH login to an already-trusted host, supports Linux (x64, arm64) hosts, and macOS hosts only when Cline Desktop runs on a Mac (Windows hosts are not supported), and connects to one host at a time. The Kanban board from your phone: Kanban, a research preview (cline/kanban), binds to 127.0.0.1:3484 by default; Cline documents starting it with KANBAN_RUNTIME_HOST=0.0.0.0 cline and opening it over Tailscale (Cline docs: Kanban remote access) to check tasks, review diffs and start new work from a phone browser (Cline blog, 2026-04-15). Binding to 0.0.0.0 listens on every network interface, and Cline notes that Kanban provides full access to your git repository and terminal, so keep it off untrusted networks.

Those features control the Cline session itself. AI Commander works alongside both: Cline still decides what to do, and AI Commander gives it MCP tools to reach your other machines — servers, GPU rigs, NAS, Windows boxes — through a host agent that only connects outbound, with no SSH keys or open ports, plus detached jobs that keep running after the chat ends. Add the AI Commander entry to the MCP config wherever the Cline agent actually runs — with Cline Desktop over SSH, that is the SSH host.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
ClineCline MCP settings / cline_mcp_settings.json + npx @aicommander/mcp
Continue~/.continue/config.yaml / .continue/mcpServers/ + stdio bridge
Cursornpx @aicommander/mcp stdio bridge → remote exec + jobs
Windsurf (Devin Desktop)~/.config/devin/mcp_config.json + stdio bridge
Claude CodeMCP remote exec + jobs on your fleet
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Gemini / Grokgemini mcp add / grok mcp add --transport http …

FAQ

Is AI Commander an alternative to Cline?
No. AI Commander is a remote-machine harness. You keep Cline (or Cursor, Claude Code, Codex, ChatGPT, Gemini, Grok, Windsurf, Continue) 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 Cline to AI Commander?
Add the stdio bridge in Cline’s MCP settings (VS Code / Cursor: open Cline → MCP Servers, or edit the cline_mcp_settings.json Cline manages) with npx -y @aicommander/mcp and AICOMMANDER_SERVER=https://aicommander.dev. First connect may open a one-time browser sign-in (DCR). Use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.
How is this different from Cline running locally only?
Local Cline is the brain in your editor. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Cline can run shell, detached jobs, and file transfer on those machines over MCP.
Does Cline have remote control?
Yes. Cline documents at least two options (checked 2026-10-23). Cline Desktop can run its sessions on one remote host over SSH: the app stays on your computer while file edits, terminal commands, Git and MCP servers run on the host; it needs key-based login to an already-trusted host, supports Linux x64 and arm64 hosts (macOS hosts only when Cline Desktop runs on a Mac; Windows hosts are not supported), and connects to one host at a time. Separately, the Cline Kanban board (a research preview) binds to localhost by default; Cline documents binding it to 0.0.0.0 and opening it from a phone over Tailscale to check tasks, review diffs and start new work, and warns that Kanban provides full access to your git repository and terminal. Keep it off untrusted networks. These control the Cline session itself. AI Commander is different: it gives Cline MCP tools to run shell commands, detached jobs and file transfer on your other machines, including Windows, through an agent that only connects outbound.

Next steps

Install the agent on a machine you control, connect Cline via MCP settings, then ask for a real task on a remote box.