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.

Quick start:
  1. Install the host agent on the machine you want your AI to control. It shows a private machine code.
  2. 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 URL https://aicommander.dev/mcp and sign in with an email code (per-client steps).
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 account features (saved aliases) with an API key instead of the sign-in, use the opencode.json variant below.

Or configure it in opencode.json

Per the OpenCode MCP docs (checked 2026-10-24), a remote server is an entry under mcp with type set to "remote" and a url. Put this in opencode.json. OpenCode starts the OAuth sign-in the first time you use the server; if it does not, run opencode mcp auth aicommander.

opencode.json — browser sign-in
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aicommander": {
      "type": "remote",
      "url": "https://aicommander.dev/mcp"
    }
  }
}

To use an AI Commander API key from the dashboard instead, turn OAuth off and send the key as a Bearer header, the way the OpenCode docs show for API-key servers. {env:AIC_API_KEY} reads the key from your environment, so it stays out of the file:

opencode.json — API key
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aicommander": {
      "type": "remote",
      "url": "https://aicommander.dev/mcp",
      "oauth": false,
      "headers": {
        "Authorization": "Bearer {env:AIC_API_KEY}"
      }
    }
  }
}

API keys only act while you have opened the AI Commander dashboard within your access window (72 hours by default); for unattended runs (CI, cron) see Credential security on Connect your AI client. OpenCode’s v2 preview docs nest servers under mcp.servers instead, so match the shape to your OpenCode version. To check the connection, run opencode mcp list.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
OpenCodeopencode mcp add aicommander --url https://aicommander.dev/mcp
Claude Codeclaude mcp add --transport http … → remote exec + jobs
Codex / ChatGPTSame MCP endpoint or REST /api/v1/exec
Cursornpx @aicommander/mcp stdio bridge → remote exec + jobs
Grok / Geminigrok mcp add --transport http … / gemini mcp add
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL
Continue / Windsurfstdio 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. For account aliases with an API key, use the opencode.json API-key config on this page. 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.
How do I add AI Commander to opencode.json?
Per the OpenCode MCP docs (checked 2026-10-24), add an entry under mcp in opencode.json with type remote and url https://aicommander.dev/mcp. OpenCode starts the OAuth sign-in the first time you use the server; if it does not, run opencode mcp auth aicommander. Check the connection with opencode mcp list.
How do I use an API key with OpenCode instead of the browser sign-in?
Set oauth to false on the aicommander entry and add an Authorization header with the value Bearer {env:AIC_API_KEY}, as in the OpenCode docs example for API-key servers. OpenCode reads {env:AIC_API_KEY} from your environment. API keys only act while you have opened the AI Commander dashboard within your access window (72 hours by default).
OpenCode says the server needs authentication or will not connect. What should I check?
Run opencode mcp list to see the connection and auth status. With the browser sign-in config, run opencode mcp auth aicommander to sign in again. With the API-key config (oauth set to false), check that AIC_API_KEY is set in the shell that starts OpenCode. With either config, check that you opened the AI Commander dashboard within your access window (72 hours by default); a lapsed window pauses keys and OAuth connectors until you open it again. opencode mcp debug aicommander tests HTTP connectivity and the OAuth discovery flow (OpenCode MCP docs, checked 2026-10-24).

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.