Keep Continue.
Give it your machines.

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

Sibling harness pages: Cursor · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Continue (stdio / config.yaml)

Continue talks to AI Commander through the same stdio MCP bridge as Cursor and Windsurf. Add this under mcpServers in ~/.continue/config.yaml (or drop a JSON/YAML file in .continue/mcpServers/ in your workspace):

mcpServers:
  - name: aicommander
    command: npx
    args:
      - -y
      - "@aicommander/mcp"
    env:
      AICOMMANDER_SERVER: https://aicommander.dev

Prefer the Claude Desktop–style JSON map? Put it at .continue/mcpServers/aicommander.json:

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

Reload Continue (or restart the editor). Full client matrix (Continue, Cursor, 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.

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 Continue 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

FAQ