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.
- Install the host agent on the machine you want your AI to control. It shows a private machine code.
- 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 URLhttps://aicommander.dev/mcpand sign in with an email code (per-client steps).
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:
Persist in user config (~/.config/amp/settings.json) or workspace
(.amp/settings.json) under amp.mcpServers:
Or store a personal remote definition on ampcode.com (available across Amp clients without a local settings file):
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
- 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 Amp 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 |
|---|---|
| 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 |
How Amp handles MCP servers
- Amp has local servers, set in
amp.mcpServersin a settings file. A URL entry there still counts as local, because your machine connects to it. - It also has remote definitions, stored on ampcode.com at personal, workspace or project level with
amp mcp remote …. For those, Amp's own servers make the connection. - Load order is
--mcp-config, then.amp/settings.json, then~/.config/amp/settings.json, then servers bundled in skills. - Servers that a repo's
.amp/settings.jsonbrings in stay inactive until you runamp mcp approve.amp mcp doctorshows what is waiting. - Remote definitions get a per-tool policy: Allow, Ask First or Disabled. Subagents cannot call Ask First tools.
- Local OAuth supports client ID metadata documents and dynamic registration.
amp mcp oauth logoutclears a stored token.
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.
- Create
aicommanderas 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. - Set
list_machines,session_status,remote_job_status,remote_job_logsandremote_job_listto Allow.remote_exec,remote_job_start,remote_job_cancel,remote_pushandremote_pullchange 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. - 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
- In multiplayer threads, MCP tools run with the thread owner's credentials. Consider keeping AI Commander out of shared threads, because it is a shell on your own machines.
- Amp suggests bundling MCP servers in skills (
mcp.jsonnext to the skill), which loads them only when the skill is used and keeps the context smaller.
FAQ
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.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.