Keep OpenHands.
Give it your machines.

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.

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: 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 · Amazon Q · Augment · Devin · 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:

legacy openhands CLI — add remote URL
$ openhands mcp add aicommander --transport http https://aicommander.dev/mcp

The legacy CLI keeps servers 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"
    }
  }
}

Agent Canvas (local or Cloud): Customize → MCP Servers → Add custom server, type SHTTP, 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.

Over the remote URL, first connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). The npx bridge does not sign in through a browser: without AICOMMANDER_TOKEN in its env it connects anonymously with a code-only first hour; set it to your API key to bind it to your account. On the remote URL, append ?anonymous=1 to skip the sign-in, for a code-only first hour. 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

Not a replacement — a multiplier

You already useAI Commander adds
OpenHandsopenhands mcp add aicommander --transport http https://aicommander.dev/mcp
Ampamp mcp add aicommander https://aicommander.dev/mcp
goosegoose session --with-streamable-http-extension "https://aicommander.dev/mcp"
Kilo Codemcp.aicommander.url → 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
Copilot / CodyHTTP MCP / cody.mcpServers + bridge
Cline / Roo Code / ZedMCP settings / context_servers + bridge or remote URL

How OpenHands handles MCP servers

Checked against OpenHands docs: MCP settings in November 2026. Client behaviour changes between releases; the official docs win if they disagree.

A workflow that suits OpenHands

OpenHands runs its agent in a sandbox, usually a container. AI Commander lets that sandboxed agent run commands on real machines outside it (as root by default), without opening SSH into the container.

  1. Add AI Commander as an SHTTP server with a bearer API key, so the connection doesn't depend on a browser sign-in.
  2. Put standing rules in the repo's AGENTS.md, for example: "Run integration tests on the staging box via remote_job_start, never on production; poll remote_job_status every few minutes."
  3. Start a new conversation, have OpenHands fix the code in its sandbox, then run the tests on the real staging machine and report the result.

Limits and gotchas in OpenHands

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. Legacy 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 Customize → MCP Servers in Agent Canvas. First connect may open a one-time browser sign-in. On the remote URL, 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.
Do I need to restart OpenHands after adding AI Commander?
No restart is needed, but MCP changes only apply to new conversations. Open a fresh conversation to get the AI Commander tools.
Can headless OpenHands automation use AI Commander?
Yes, with a bearer API key in the server's auth settings.
Should I use the npx stdio bridge with OpenHands?
Prefer the HTTP endpoint. OpenHands' docs advise against stdio servers in production.
What does Test connection in OpenHands tell me about AI Commander?
It connects with the saved auth settings and reports how many tools the server returned. For AI Commander you should see tools such as session_status, list_machines and remote_exec before you start a conversation.

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.