Keep Factory.
Give Droid your machines.

AI Commander is not an alternative to Factory, 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, Augment Code, Devin, JetBrains Junie, Kiro, or Warp. 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.

Positioning in one line: Factory's Droids stay your coding agent; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

Sibling harness pages: Claude Code · Codex · Cursor · GitHub Copilot · Devin · Kiro · Warp · Junie · OpenHands · Gemini — and the rest on Connect your AI client.

Connect Factory Droid (remote MCP)

Factory’s Droid (Factory MCP docs) supports remote MCP servers over Streamable HTTP. Add AI Commander from the CLI:

terminal — add remote MCP
droid mcp add aicommander https://aicommander.dev/mcp --type http

Then type /mcp inside Droid to complete the one-time browser sign-in (OAuth with Dynamic Client Registration) and see the AI Commander tools. droid mcp list shows connection status. Servers added this way land in your user config, ~/.factory/mcp.json — which you can also edit by hand:

~/.factory/mcp.json — remote MCP
{
  "mcpServers": {
    "aicommander": {
      "type": "http",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

A project-scope .factory/mcp.json in the repo root shares the server with your team — but it is committed, so never put an Authorization header or API key there. Keep secrets in the user file and reference an environment variable (for example "Bearer ${AIC_API_KEY}"), which Droid expands at connect time.

Prefer a local stdio bridge?

terminal — stdio bridge
droid mcp add aicommander "npx -y @aicommander/mcp" \
  --env AICOMMANDER_SERVER=https://aicommander.dev

Keep AI Commander tools behind Droid’s confirmation prompts at first; long builds and training runs are good candidates for detached jobs, and you can hide tools you do not want a Droid to call with disabledTools.

Full client matrix (Factory, Kiro, Warp, Junie, 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.

For a code-only first hour without the OAuth flow, append ?anonymous=1 to the MCP URL. For optional account features (saved aliases), pass a Bearer API key in headers. Commands and options can differ between Droid versions — check the linked Factory docs for your build.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Factory (Droid)droid mcp add aicommander https://aicommander.dev/mcp --type http
KiromcpServers.aicommander.url → https://aicommander.dev/mcp in ~/.kiro/settings/mcp.json
WarpSettings → Agents → MCP servers → + Add → https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursor / Continue / Windsurfnpx @aicommander/mcp stdio bridge

FAQ

Is AI Commander an alternative to Factory?
No. AI Commander is NOT an alternative to Factory. It is a remote-machine harness. You keep Factory's Droids (or 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, Augment Code, Devin, JetBrains Junie, Kiro, or Warp) as the AI coding agent. 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 Factory Droid to AI Commander?
Run droid mcp add aicommander https://aicommander.dev/mcp --type http, then type /mcp inside Droid to finish the one-time browser sign-in (OAuth). Or add mcpServers.aicommander with type http and url https://aicommander.dev/mcp to ~/.factory/mcp.json. Prefer stdio? Use command npx with args -y @aicommander/mcp. Use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.
How is this different from Droid working in my repo?
Factory's Droids work on the repo and environment they run in. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Droid can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

Install the agent on a machine you control, add AI Commander to Droid (droid mcp add … --type http or npx -y @aicommander/mcp), then ask Droid for a real task on a remote box.