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.

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: 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 · Amazon Q · 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

Not a replacement — a multiplier

You already useAI Commander adds
GitHub Copilotcopilot mcp add --transport http aicommander https://aicommander.dev/mcp
Kilo Codemcp.aicommander.url → https://aicommander.dev/mcp
Ampamp mcp add aicommander https://aicommander.dev/mcp
goosegoose session --with-streamable-http-extension "https://aicommander.dev/mcp"
Qwen Codeqwen mcp add --transport http aicommander https://aicommander.dev/mcp
OpenCodeopencode mcp add aicommander --url https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursornpx @aicommander/mcp stdio bridge → remote exec + jobs
Grok / Geminigrok mcp add --transport http … / gemini mcp add
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL
Continue / Windsurfstdio bridge in Continue / Windsurf MCP config

How GitHub Copilot handles MCP servers

Checked against GitHub docs: Copilot CLI and VS Code docs: MCP servers in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits GitHub Copilot

  1. In a Copilot CLI session, ask it to start the training or migration run with remote_job_start and note the job id.
  2. Turn on experimental features with /experimental on, then schedule a check-in such as /every 30m check AI Commander job <id> with remote_job_status and summarise the last log lines. Scheduled prompts only fire while that interactive session is running.
  3. When the job ends, ask Copilot to pull the result file with remote_pull (file courier, Pro) and open a pull request with the numbers.

Limits and gotchas in GitHub Copilot

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.
Does the server I added in VS Code also work in Copilot CLI?
It does if you saved it to the Copilot Global scope, which writes ~/.copilot/mcp-config.json. A server that only lives in .vscode/mcp.json is an editor-only setting.

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.