Keep Gemini.
Give it your machines.

AI Commander is not an alternative to Gemini, ChatGPT, Claude Code, Cursor, Grok, or Codex. 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: Gemini 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: Claude Code · Cursor · Grok · Codex · ChatGPT.

Connect Gemini CLI (HTTP MCP)

Gemini CLI talks to AI Commander over remote Streamable HTTP MCP. One command — pass --transport http and use user scope so it lands in ~/.gemini/settings.json:

gemini CLI

$ gemini mcp add -s user --transport http aicommander https://aicommander.dev/mcp

Prefer a local stdio bridge? One command (or put the same block under mcpServers in ~/.gemini/settings.json):

gemini CLI · stdio

$ gemini mcp add -s user -e AICOMMANDER_SERVER=https://aicommander.dev aicommander npx -y @aicommander/mcp

Or set httpUrl / command+args under mcpServers.aicommander in ~/.gemini/settings.json. Use httpUrl (not legacy SSE url) for Streamable HTTP. Full client matrix (Gemini, Codex, ChatGPT, Claude Code, Cursor, Grok, REST): Connect your AI client.

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 where your client 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 Gemini 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
Gemini CLI	`gemini mcp add --transport http aicommander …` → remote exec + jobs
Codex CLI	`codex mcp add aicommander --url …` → remote exec + jobs
ChatGPT / OpenAI	Custom MCP connector or plain REST `/api/v1/exec`
Grok / `grok` CLI	`grok mcp add --transport http …` → remote exec + jobs
Claude Code	MCP remote exec + jobs on your fleet
Cursor	`npx @aicommander/mcp` stdio bridge → remote exec + jobs

FAQ

Is AI Commander an alternative to Gemini?

No. AI Commander is a remote-machine harness. You keep Gemini (or ChatGPT, Claude Code, Cursor, Grok, Codex) 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 Gemini CLI to AI Commander?

Run: gemini mcp add -s user --transport http aicommander https://aicommander.dev/mcp — use --transport http for Streamable HTTP. First connect may open a one-time browser sign-in (/mcp auth). Prefer a local stdio bridge? gemini mcp add -s user -e AICOMMANDER_SERVER=https://aicommander.dev aicommander npx -y @aicommander/mcp. Use ?anonymous=1 for a code-only first hour.

How is this different from Gemini running locally only?

Local Gemini is the brain on your laptop. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so Gemini can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

Install the agent on a machine you control, connect Gemini via gemini mcp add, then ask for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep Gemini.Give it your machines.