AI Commander · Harness

Keep Claude Code, Codex, and ChatGPT.
Give them your machines.

AI Commander is not an alternative to Claude Code, Codex, or ChatGPT. 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: your AI stays the brain; AI Commander is the hands on the box — servers, GPU rigs, NAS, laptops — with no inbound ports and no exposed SSH.

Connect in one command

Claude Code
$ claude mcp add --transport http aicommander https://aicommander.dev/mcp
Codex
$ codex mcp add aicommander --url https://aicommander.dev/mcp

ChatGPT / Claude Desktop: add custom connector URL https://aicommander.dev/mcp (one-time browser sign-in). Full client matrix: Connect your AI client.

What you get that the chat alone cannot

Not a replacement — a multiplier

You already useAI Commander adds
Claude CodeMCP remote exec + jobs on your fleet
CodexSame MCP endpoint; aliases after sign-in
ChatGPTCustom MCP connector or plain REST /api/v1/exec
Cursor / other MCP clientsnpx @aicommander/mcp stdio bridge

FAQ

Is AI Commander an alternative to Claude Code or Codex?
No. AI Commander is a remote-machine harness. You keep Claude Code, Codex, ChatGPT, or Cursor 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 Claude Code to AI Commander?
Run: claude mcp add --transport http aicommander https://aicommander.dev/mcp — then install the agent on the target machine and ask Claude to use the machine code or saved alias.
How do I connect Codex?
Run: codex mcp add aicommander --url https://aicommander.dev/mcp — pass --url before the address. First connect opens a one-time browser sign-in.

Next steps

Install the agent on a machine you control, connect Claude Code / Codex / ChatGPT, then ask for a real task.