Keep Amazon Q Developer.
Give it your machines.

AI Commander is not an alternative to Amazon Q Developer, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, or Kilo 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.

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

Connect Amazon Q Developer (MCP HTTP)

Amazon Q Developer (MCP docs) supports remote MCP servers over HTTP in the CLI / Q Chat, and MCP in the IDE chat. Point it at AI Commander’s hosted MCP endpoint:

Amazon Q agent config — remote HTTP

{
  "mcpServers": {
    "aicommander": {
      "type": "http",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

CLI / Q Chat: add or edit the remote server in your Amazon Q agent configuration (qchat mcp add for managed entries; remote HTTP uses type + url as above). After connect, run /mcp in the CLI if OAuth is required and follow the browser URL. IDE: Amazon Q Chat → Configure MCP servers → add an HTTP server named aicommander with URL https://aicommander.dev/mcp (global ~/.aws/amazonq/ or workspace .amazonq/). Prefer a local stdio bridge?

stdio bridge

$ npx -y @aicommander/mcp

Wire that command under mcpServers.aicommander with command/args (and optional env AICOMMANDER_SERVER=https://aicommander.dev) in ~/.aws/amazonq/mcp.json or your agent default.json — same pattern as other stdio MCP clients.

Full client matrix (Amazon Q, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Amazon Q MCP docs: Using MCP with Amazon Q Developer · CLI MCP config · IDE MCP config.

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 Amazon Q build 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 Amazon Q 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

You already use	AI Commander adds
Amazon Q Developer	`type: http` → `https://aicommander.dev/mcp` (or `npx -y @aicommander/mcp`)
OpenHands	`openhands mcp add aicommander --transport http https://aicommander.dev/mcp`
Amp	`amp mcp add aicommander https://aicommander.dev/mcp`
goose	`goose session --with-streamable-http-extension "https://aicommander.dev/mcp"`
Kilo Code	`mcp.aicommander.url → https://aicommander.dev/mcp`
Claude Code	`claude mcp add --transport http …` → remote exec + jobs
Codex / ChatGPT	Same MCP endpoint or REST `/api/v1/exec`
Cursor / Continue / Windsurf	`npx @aicommander/mcp` stdio bridge
Copilot / Cody	HTTP MCP / `cody.mcpServers` + bridge
Cline / Roo Code / Zed	MCP settings / `context_servers` + bridge or remote URL

FAQ

Is AI Commander an alternative to Amazon Q Developer?

No. AI Commander is a remote-machine harness. You keep Amazon Q Developer (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) 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 Amazon Q Developer to AI Commander?

Add AI Commander as a remote MCP server for Amazon Q. CLI / Q Chat: configure a remote HTTP server with type http and url https://aicommander.dev/mcp in your Amazon Q agent config (or use qchat mcp add for a stdio bridge with npx -y @aicommander/mcp). IDE: Amazon Q Chat → Configure MCP servers → add HTTP transport pointing at https://aicommander.dev/mcp, or edit ~/.aws/amazonq/mcp.json (legacy) / agent default.json under mcpServers. 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 Amazon Q running locally only?

Local Amazon Q Developer is the brain in your IDE chat or Q CLI. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Amazon Q can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

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

Install the agent Setup guides Remote coding agents

Keep Amazon Q Developer.Give it your machines.