Keep Warp.
Give it your machines.

AI Commander is not an alternative to Warp, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, Kilo Code, OpenHands, Amazon Q Developer, Augment Code, Devin, or JetBrains Junie. 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: Junie · Cursor · GitHub Copilot · Cody · OpenHands · Amazon Q · Augment · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini · Cua Spaces · Kiro.

Connect Warp (remote MCP)

Warp, the agentic development environment built around the terminal (Warp MCP docs), lets its local agents use MCP servers added under Settings → Agents → MCP servers (or Warp Drive → MCP Servers). Per Warp’s docs, a Streamable HTTP or SSE Server (URL) needs only a url (plus optional headers), and Warp opens a browser sign-in for OAuth-protected servers and stores the credentials on your device. Click + Add and paste:

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

Prefer a file that follows you across repos? Warp also reads file-based servers from ~/.warp/.mcp.json (global, auto-spawned by default) or .warp/.mcp.json at the project root (project scope, which Warp only starts after you approve it). The built-in /agent-add-mcp skill can write that entry for you, with your approval. Do not commit secrets: if you add an Authorization header with an API key, keep it in the global file or in Warp settings.

Prefer a local stdio bridge?

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

Running Warp’s cloud agents instead of local ones? They take MCP servers from the CLI or an agent config file, and per Warp’s docs a raw OAuth url without an Authorization header cannot be completed mid-run — pass a Bearer API key in headers or set the server up as a managed installation first (see Warp’s cloud-agent MCP docs).

Full client matrix (Warp, Kiro, Junie, Augment, Devin, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, OpenHands, Amazon Q, 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. For optional account features (saved aliases), pass a Bearer API key in headers. Menu names and options can differ between Warp versions — check the linked Warp docs for your build.

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, test suites, and training on the box that has the repo.
• Fleet list + GPU facts so Warp 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