Keep Amp.
Give it your machines.

AI Commander is not an alternative to Amp, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, or goose. 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: Amp 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 · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect Amp (MCP URL)

Amp (MCP docs) is a coding agent with first-class local and remote MCP servers. Point it at AI Commander’s hosted MCP endpoint:

amp CLI — add remote URL
$ amp mcp add aicommander https://aicommander.dev/mcp

Persist in user config (~/.config/amp/settings.json) or workspace (.amp/settings.json) under amp.mcpServers:

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

Or store a personal remote definition on ampcode.com (available across Amp clients without a local settings file):

amp mcp remote
$ amp mcp remote --personal add aicommander https://aicommander.dev/mcp

Full client matrix (Amp, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, OpenCode, Qwen Code, goose, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Amp MCP docs: Customize → MCP.

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), add a header in config: headers: { Authorization: "Bearer <your-key>" } (Amp supports ${VAR_NAME} env substitution in settings).

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
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 Amp handles MCP servers

Checked against Amp docs: MCP in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits Amp

Amp's cloud runs (orbs) are useful for work that should keep going after you close the laptop. AI Commander lets those runs reach machines that live in your home or office.

  1. Create aicommander as a personal remote definition. Orbs don't read your local settings file and can't open a browser for OAuth, so a local entry won't follow you there.
  2. Set list_machines, session_status, remote_job_status, remote_job_logs and remote_job_list to Allow. remote_exec, remote_job_start, remote_job_cancel, remote_push and remote_pull change or copy out data on your machines: keep them on Ask First unless the run is meant to be unattended. Ask First pauses a run until you answer, and subagents can't use those tools at all.
  3. From the orb, start the long step with remote_job_start, finish the code change, and check the job before opening the pull request.

Limits and gotchas in Amp

FAQ

Is AI Commander an alternative to Amp?
No. AI Commander is a remote-machine harness. You keep Amp (or Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose) 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 Amp to AI Commander?
Add AI Commander as a remote MCP URL in Amp. Quick CLI: amp mcp add aicommander https://aicommander.dev/mcp. Or set amp.mcpServers.aicommander.url to "https://aicommander.dev/mcp" in ~/.config/amp/settings.json (user) or .amp/settings.json (workspace). Or use amp mcp remote --personal add aicommander https://aicommander.dev/mcp for a definition stored on ampcode.com. 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 Amp running locally only?
Local Amp is the brain in your editor, TUI, or orb. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Amp can run shell, detached jobs, and file transfer on those machines over MCP.
Can an Amp orb use AI Commander?
Yes, but not through your personal settings file or a sign-in started inside the orb. Use a remote definition on ampcode.com (Amp's servers make the connection, and amp mcp remote handles its sign-in) or a server in the repository's .amp/settings.json. Amp's MCP docs describe how orbs handle secrets.
Should teammates in a multiplayer Amp thread use my AI Commander connection?
Usually not. Tools in those threads use the owner's credentials, so anyone in the thread could run commands on your machines. Turn the server off for multiplayer use, or keep every tool that changes a machine (remote_exec, remote_job_start, remote_job_cancel, remote_push) on Ask First.

Next steps

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