Keep OpenCode.
Give it your machines.

AI Commander is not an alternative to OpenCode, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, or Zed. 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: OpenCode 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: Cursor · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect OpenCode (MCP CLI)

OpenCode is an open-source coding agent CLI with native remote HTTP MCP support. Point it at AI Commander’s hosted MCP endpoint:

opencode CLI

$ opencode mcp add aicommander --url https://aicommander.dev/mcp

Full client matrix (OpenCode, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Continue, Windsurf, Cline, Roo Code, Zed, 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. For optional account features (saved aliases), add --env AICOMMANDER_TOKEN=<your-key> to the command.

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 OpenCode 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
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

FAQ

Is AI Commander an alternative to OpenCode?

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

Run: opencode mcp add aicommander --url https://aicommander.dev/mcp — then install the agent on the target machine and ask OpenCode to use the machine code or saved alias. First connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). Use ?anonymous=1 for a code-only first hour. Optional: add --env AICOMMANDER_TOKEN=<your-key> for account aliases. See /howto/ for the full matrix.

How is this different from OpenCode running locally only?

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

Next steps

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

Install the agent Setup guides Remote coding agents

Keep OpenCode.Give it your machines.