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.
- Install the host agent on the machine you want your AI to control. It shows a private machine code.
- 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 URLhttps://aicommander.dev/mcpand sign in with an email code (per-client steps).
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:
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
- 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 Qwen Code picks the right machine before it burns an hour.
- File courier (Pro) for checkpoints and diffs up to 100 MiB.
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 use | AI Commander adds |
|---|---|
| Qwen Code | qwen mcp add --transport http aicommander https://aicommander.dev/mcp |
| 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
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.