Keep Augment Code.
Give it your machines.

AI Commander is not an alternative to Augment Code, 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, or Devin. 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.

Positioning in one line: Augment Code 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 · GitHub Copilot · Cody · OpenHands · Amazon Q · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Augment Code (MCP HTTP)

Augment Code (Auggie MCP docs · IDE MCP setup) supports remote MCP servers over HTTP in the Auggie CLI and in the IDE Settings Panel. Point it at AI Commander’s hosted MCP endpoint:

Auggie CLI — remote HTTP
$ auggie mcp add aicommander --transport http --url https://aicommander.dev/mcp

That writes ~/.augment/settings.json (or use --project / --local for repo-scoped settings). Equivalent JSON under mcpServers:

~/.augment/settings.json — remote HTTP
{
  "mcpServers": {
    "aicommander": {
      "type": "http",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

IDE: Augment Settings Panel → MCP → Add remote MCP (or Import from JSON) with the same type + url. Prefer a local stdio bridge?

stdio bridge
$ auggie mcp add aicommander --command npx --args "-y @aicommander/mcp"

Or wire npx -y @aicommander/mcp under mcpServers.aicommander with command/args (and optional env AICOMMANDER_SERVER=https://aicommander.dev) — same pattern as other stdio MCP clients.

Full client matrix (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. Augment MCP docs: Integrations and MCP · Setup MCP servers.

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 header where your Augment build supports it.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Augment Codeauggie mcp add aicommander --transport http --url https://aicommander.dev/mcp
DevinSettings → MCP → custom HTTP → https://aicommander.dev/mcp (or devin mcp add)
Amazon Q Developertype: http → https://aicommander.dev/mcp (or npx -y @aicommander/mcp)
OpenHandsopenhands mcp add aicommander --transport http https://aicommander.dev/mcp
Ampamp mcp add aicommander https://aicommander.dev/mcp
goosegoose session --with-streamable-http-extension "https://aicommander.dev/mcp"
Kilo Codemcp.aicommander.url → https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursor / Continue / Windsurfnpx @aicommander/mcp stdio bridge
Copilot / CodyHTTP MCP / cody.mcpServers + bridge
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL

FAQ

Is AI Commander an alternative to Augment Code?
No. AI Commander is a remote-machine harness. You keep Augment Code (or 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, Devin) 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 Augment Code to AI Commander?
Add AI Commander as a remote MCP server for Augment. CLI: auggie mcp add aicommander --transport http --url https://aicommander.dev/mcp (writes ~/.augment/settings.json). Or paste type http + url https://aicommander.dev/mcp under mcpServers in settings.json / Import from JSON in the Augment Settings Panel. Prefer stdio? auggie mcp add aicommander --command npx --args "-y @aicommander/mcp". First connect may open a one-time browser sign-in (OAuth). Use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.
How is this different from Augment running locally only?
Local Augment Code is the brain in your IDE or Auggie CLI. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Augment can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

Install the agent on a machine you control, connect Augment Code via remote HTTP MCP (or npx -y @aicommander/mcp), then ask for a real task on a remote box.