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.
- 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 · 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 · Cua Spaces.
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.
Over the remote URL, first connect may open a one-time browser sign-in (OAuth Dynamic Client Registration).
The npx bridge does not sign in through a browser: without AICOMMANDER_TOKEN in its env it connects anonymously with a code-only first hour; set it to your API key to bind it to your account.
On the remote URL, append ?anonymous=1 to skip the sign-in, for a code-only first hour.
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 |
How Augment Code handles MCP servers
- Augment offers three ways in: one-click "Easy MCP" integrations for a fixed list of services, "+ Add remote MCP" in the settings panel (HTTP or SSE), and Import from JSON for an existing
mcpServersblock. - AI Commander isn't in the Easy MCP list. Use "+ Add remote MCP" with
https://aicommander.dev/mcp, or import the JSON you already use elsewhere. An importednpxbridge block withoutAICOMMANDER_TOKENruns anonymously, code-only. ${workspaceFolder}is expanded in commands, arguments and URLs, but only when Augment runs inside a workspace.- MCP Tool Search (
augment.mcp.enableToolSearch, off by default) hides tool definitions behind two meta-tools,find-toolandexecute-tool. That keeps the context small when many servers are connected. Approval rules still match the real tool names. - Augment bills
find-toolcalls separately as tool-search activity. - Augment's docs warn that not every MCP server works well with its agent. Check the tool list after you add one.
Checked against Augment docs: MCP in November 2026. Client behaviour changes between releases; the official docs win if they disagree.
A workflow that suits Augment Code
Augment's agent tends to work across a large codebase. AI Commander adds the step it can't take on its own: running the code on the real machine where the bug shows up.
- Add it as a remote HTTP server with an
Authorization: BearerAPI key header, or import an existingaicommanderblock that setsAICOMMANDER_TOKEN. - Ask: "Reproduce the crash from issue 412 on the staging box. Run the failing command with
remote_execand show me the stack trace." - Once the fix is in, ask Augment to run the full suite on the same box with
remote_job_startand report the result.
Limits and gotchas in Augment Code
- With Tool Search on, the agent has to find AI Commander's tools before it can use them. If it seems unaware of them, name the server in your prompt.
- A
${workspaceFolder}path in an imported config won't resolve when Augment runs outside a workspace. - AI Commander exposes eleven tools. If it is your only MCP server, Tool Search adds a step without saving much context.
FAQ
npx bridge never does: it connects anonymously unless AICOMMANDER_TOKEN is set in its env. On the remote URL, use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.find-tool call, shown as Tool Search activity in your usage dashboard.aicommander block you use in Claude Desktop or Cursor. If that block is the npx bridge, add AICOMMANDER_TOKEN to its env, or it connects anonymously.find-tool until the agent searches for them. Mention AI Commander or the machine in your prompt, or turn Tool Search off when AI Commander is one of only a few servers.remote_job_start, which returns a job id at once; the job keeps running on the machine after the chat moves on. Later, ask for remote_job_status or remote_job_logs with that id, even from a new conversation.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.