Keep Zed.
Give it your machines.

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

Connect Zed (context_servers)

Zed is a high-performance code editor with a built-in Agent Panel and native MCP support (Zed calls them context servers). Add AI Commander under context_servers in Zed’s settings (Settings → AI → MCP Servers, or command palette zed: open settings file):

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

Prefer a remote HTTP MCP endpoint? Zed also accepts a URL entry (OAuth / DCR on first connect):

{
  "context_servers": {
    "aicommander": {
      "url": "https://aicommander.dev/mcp"
    }
  }
}

Full client matrix (Zed, Cursor, Continue, Windsurf, Cline, Roo Code, 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 Zed 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