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.

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: Zed 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 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):

settings.json — local stdio bridge
{
  "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):

settings.json — remote MCP
{
  "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.

Over the remote URL, first connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). The npx bridge does not sign in through a browser: without AICOMMANDER_TOKEN in its env it connects anonymously with a code-only first hour; set it to your API key to bind it to your account. On the remote URL, append ?anonymous=1 to skip the sign-in, for a code-only first hour, where your client supports it.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Zedcontext_servers in settings.json — local npx @aicommander/mcp or remote https://aicommander.dev/mcp
Cursornpx @aicommander/mcp stdio bridge → remote exec + jobs
Continue~/.continue/config.yaml / .continue/mcpServers/ + stdio bridge
Cline / Roo CodeMCP settings JSON + npx @aicommander/mcp
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 …

How Zed handles MCP servers

Checked against Zed docs: Model Context Protocol in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Zed

Zed's agent profiles let you build a narrow "remote ops" mode that can only touch your machines through AI Commander.

  1. Create a custom profile that enables the aicommander tools and turns off the built-in terminal tool, so remote work can't end up running on your laptop by mistake.
  2. Set mcp:aicommander:remote_exec and mcp:aicommander:remote_job_start to confirm and the read-only tools such as mcp:aicommander:list_machines to allow.
  3. In that profile, ask: "Check why nginx on the edge box returns 502s." The agent calls remote_exec for logs and config, and each command waits for your confirmation.

Limits and gotchas in Zed

FAQ

Is AI Commander an alternative to Zed?
No. AI Commander is a remote-machine harness. You keep Zed (or Cursor, Claude Code, Codex, ChatGPT, Gemini, Grok, Windsurf, Continue, Cline, Roo Code) 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 Zed to AI Commander?
Add AI Commander under context_servers in Zed’s settings.json (Settings → AI → MCP Servers, or zed: open settings file): either a local server with command npx / args ["-y", "@aicommander/mcp"] and AICOMMANDER_SERVER=https://aicommander.dev, or a remote server with url https://aicommander.dev/mcp. The remote URL may ask for a one-time browser sign-in (OAuth); the npx bridge never does: it connects anonymously unless AICOMMANDER_TOKEN is set in its env. On the remote URL, use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.
How is this different from Zed running locally only?
Local Zed Agent 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 Zed can run shell, detached jobs, and file transfer on those machines over MCP.
Does Claude Code inside Zed see my AI Commander server?
As an external agent over ACP, yes: Zed forwards its context servers. In a terminal thread, no. Claude Code then uses its own MCP config, so add AI Commander there.
How do I make Zed ask before every remote command?
Set the per-tool permissions mcp:aicommander:remote_exec and mcp:aicommander:remote_job_start to confirm, or set agent.tool_permissions.default to confirm (v0.224.0+).

Next steps

Install the agent on a machine you control, connect Zed via context_servers, then ask for a real task on a remote box.