Keep Augment Code.
Give it your machines.
AI Commander is not an alternative to Augment Code, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, Kilo Code, OpenHands, Amazon Q Developer, or Devin. 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.
Sibling harness pages: Cursor · GitHub Copilot · Cody · OpenHands · Amazon Q · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.
Connect Augment Code (MCP HTTP)
Augment Code (Auggie MCP docs · IDE MCP setup) supports remote MCP servers over HTTP in the Auggie CLI and in the IDE Settings Panel. Point it at AI Commander’s hosted MCP endpoint:
That writes ~/.augment/settings.json (or use --project / --local for repo-scoped settings).
Equivalent JSON under mcpServers:
{
"mcpServers": {
"aicommander": {
"type": "http",
"url": "https://aicommander.dev/mcp"
}
}
}
IDE: Augment Settings Panel → MCP → Add remote MCP (or Import from JSON) with the same
type + url. Prefer a local stdio bridge?
Or wire npx -y @aicommander/mcp under mcpServers.aicommander with
command/args (and optional env
AICOMMANDER_SERVER=https://aicommander.dev) — same pattern as other stdio MCP clients.
Full client matrix (Augment, Devin, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, OpenHands, Amazon Q, REST): Connect your AI client. Augment MCP docs: Integrations and MCP · Setup MCP servers.
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 Augment 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 Augment 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 |
|---|---|
| Augment Code | auggie mcp add aicommander --transport http --url https://aicommander.dev/mcp |
| Devin | Settings → MCP → custom HTTP → https://aicommander.dev/mcp (or devin mcp add) |
| 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
Next steps
Install the agent on a machine you control, connect Augment Code via remote HTTP MCP (or npx -y @aicommander/mcp), then ask for a real task on a remote box.