Keep Qwen Code.
Give it your machines.

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

Qwen Code is Alibaba's open-source coding agent CLI with native remote HTTP MCP support (httpUrl / Streamable HTTP). Point it at AI Commander’s hosted MCP endpoint:

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

Full client matrix (Qwen Code, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, OpenCode, 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), pass --header "Authorization: Bearer <your-key>" or configure headers in ~/.qwen/settings.json.

What you get that the chat alone cannot

Qwen Code remote control and AI Commander

Qwen Code has its own ways to reach a running session. Local Control (qwen serve --local-control, or Control → Local Control… in the desktop app) prints a QR code so a phone on the same trusted network can join the live Web Shell session, follow the output and answer permission prompts (Qwen Code docs). Local Control is LAN-only for now: Qwen Code says using it over the public internet is not supported yet (Qwen Code weekly, 2026-08-13). Separately, qwen serve can listen on a non-loopback address with a bearer token for a remote Web Shell, and it can run experimental daemon-managed Channels (daemon mode docs) that let you message Qwen Code from Telegram, WeChat or DingTalk (Qwen Code weekly, 2026-04-09).

Those features control the Qwen Code session itself. AI Commander works alongside them: Qwen Code still decides what to do, and AI Commander gives it MCP tools to reach your other machines — servers, GPU rigs, NAS, Windows boxes — through a host agent that only connects outbound, with no SSH keys or open ports, plus detached jobs that keep running after the session ends.

Not a replacement — a multiplier

You already useAI Commander adds
Qwen Codeqwen mcp add --transport http aicommander https://aicommander.dev/mcp
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 Qwen Code?
No. AI Commander is a remote-machine harness. You keep Qwen Code (or Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode) 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 Qwen Code to AI Commander?
Run: qwen mcp add --transport http aicommander https://aicommander.dev/mcp — then install the agent on the target machine and ask Qwen Code 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: pass --header Authorization: Bearer <your-key> for account aliases. See /howto/ for the full matrix.
How is this different from Qwen Code running locally only?
Local Qwen Code 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 Qwen Code can run shell, detached jobs, and file transfer on those machines over MCP.
Does Qwen Code have remote control?
Yes, on its own terms. Local Control (qwen serve --local-control, or Control → Local Control in the desktop app) lets a phone on the same trusted network join a live Web Shell session with a QR pairing code; Qwen Code says Local Control does not work over the public internet yet. Separately, qwen serve can listen on a non-loopback address with a bearer token, and its experimental Channels connect it to chat apps such as Telegram, WeChat and DingTalk. These control the Qwen Code session itself. AI Commander is different: it gives Qwen Code MCP tools to run shell commands, detached jobs and file transfer on your other machines through an agent that only connects outbound.

Next steps

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