Keep OpenHands.
Give it your machines.

Q: How do I connect OpenHands to AI Commander?

Add AI Commander as a remote MCP URL in OpenHands. Quick CLI: openhands mcp add aicommander --transport http https://aicommander.dev/mcp. Or edit ~/.openhands/mcp.json under mcpServers with a url entry for https://aicommander.dev/mcp (OAuth on first connect). Or use Settings → MCP in the OpenHands UI / Local GUI. First connect may open a one-time browser sign-in. Use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.

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

Connect OpenHands (MCP HTTP)

OpenHands (CLI MCP docs) connects to remote MCP servers over HTTP (and stdio / SSE). Point it at AI Commander’s hosted MCP endpoint:

openhands CLI — add remote URL

$ openhands mcp add aicommander --transport http https://aicommander.dev/mcp

Persist in ~/.openhands/mcp.json under mcpServers (restart the conversation after edits; use /mcp in-chat to check status):

~/.openhands/mcp.json

{
  "mcpServers": {
    "aicommander": {
      "url": "https://aicommander.dev/mcp",
      "auth": "oauth"
    }
  }
}

Local GUI / Cloud: Settings → MCP, or config.toml [mcp] shttp_servers with the same URL. Prefer a local stdio bridge?

stdio bridge

$ openhands mcp add aicommander --transport stdio --env AICOMMANDER_SERVER=https://aicommander.dev npx -- -y @aicommander/mcp

Full client matrix (OpenHands, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. OpenHands MCP docs: CLI → MCP Servers.

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), pass a Bearer API key header where your OpenHands 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 OpenHands 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
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

FAQ

Is AI Commander an alternative to OpenHands?

No. AI Commander is a remote-machine harness. You keep OpenHands (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) 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 OpenHands to AI Commander?

Add AI Commander as a remote MCP URL. CLI: openhands mcp add aicommander --transport http https://aicommander.dev/mcp. Or edit ~/.openhands/mcp.json under mcpServers with "url": "https://aicommander.dev/mcp" (and "auth": "oauth" when you want the browser sign-in). Or Settings → MCP in the OpenHands UI. First connect may open a one-time browser sign-in. Use ?anonymous=1 for a code-only first hour. See /howto/ for the full matrix.

How is this different from OpenHands running locally only?

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

Next steps

Install the agent on a machine you control, connect OpenHands via openhands mcp add … --transport http, then ask for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep OpenHands.Give it your machines.