Keep GitHub Copilot.
Give it your machines.

AI Commander is not an alternative to GitHub Copilot, Claude Code, Codex, ChatGPT, Cursor, 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: GitHub Copilot 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 · goose · Amp · Kilo Code · GitHub Copilot · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect GitHub Copilot (MCP HTTP)

GitHub Copilot (Copilot CLI MCP docs) supports remote MCP over HTTP (Streamable HTTP) in Copilot CLI, VS Code Copilot Chat / agent mode, and the Copilot cloud agent. Point it at AI Commander’s hosted MCP endpoint:

Copilot CLI — add remote MCP

$ copilot mcp add --transport http aicommander https://aicommander.dev/mcp

Or persist under mcpServers in ~/.copilot/mcp-config.json (same shape works for many Copilot agent MCP configs):

~/.copilot/mcp-config.json

{ "mcpServers": { "aicommander": { "type": "http", "url": "https://aicommander.dev/mcp", "tools": ["*"] } } }

Optional Bearer header for account aliases:

headers (optional)

"headers": { "Authorization": "Bearer YOUR_AICOMMANDER_KEY" }

Full client matrix (GitHub Copilot, Kilo Code, Amp, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, OpenCode, Qwen Code, goose, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Copilot MCP docs: Add MCP servers (CLI) · Configure MCP (cloud agent).

First connect may open a one-time browser sign-in (OAuth). For a code-only first hour without that flow, append ?anonymous=1 to the MCP URL.

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 Copilot 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
GitHub Copilot	`copilot mcp add --transport http aicommander https://aicommander.dev/mcp`
Kilo Code	`mcp.aicommander.url → https://aicommander.dev/mcp`
Amp	`amp mcp add aicommander https://aicommander.dev/mcp`
goose	`goose session --with-streamable-http-extension "https://aicommander.dev/mcp"`
Qwen Code	`qwen mcp add --transport http aicommander https://aicommander.dev/mcp`
OpenCode	`opencode mcp add 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	`npx @aicommander/mcp` stdio bridge → remote exec + jobs
Grok / Gemini	`grok mcp add --transport http …` / `gemini mcp add`
Cline / Roo Code / Zed	MCP settings / `context_servers` + bridge or remote URL
Continue / Windsurf	stdio bridge in Continue / Windsurf MCP config

FAQ

Is AI Commander an alternative to GitHub Copilot?

No. AI Commander is a remote-machine harness. You keep GitHub Copilot (or Claude Code, Codex, ChatGPT, Cursor, 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 GitHub Copilot to AI Commander?

Add AI Commander as a remote MCP server for Copilot. Copilot CLI: copilot mcp add --transport http aicommander https://aicommander.dev/mcp. Or edit ~/.copilot/mcp-config.json under mcpServers with type http and url https://aicommander.dev/mcp. In VS Code Copilot Chat / agent MCP settings, add the same HTTP URL. First connect may open a one-time browser sign-in (OAuth). Use ?anonymous=1 for a code-only first hour. Optional: set headers Authorization: Bearer <your-key> for account aliases. See /howto/ for the full matrix.

How is this different from Copilot running locally only?

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

Next steps

Install the agent on a machine you control, connect GitHub Copilot via MCP HTTP to https://aicommander.dev/mcp, then ask for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep GitHub Copilot.Give it your machines.