Keep ChatGPT.
Give it your machines.
AI Commander is not an alternative to ChatGPT, OpenAI, GPT, Codex, Claude Code, Cursor, or Grok.
It is the remote-machine harness those tools plug into over MCP — including OpenAI submodels such as
Astra (gpt-6-astra):
outbound-only shell, detached jobs that outlive the chat, and file transfer on hardware you already own or rent, like the box in your closet or a VPS.
- 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: Claude Code · Cursor · Grok · Codex · Roo Code · Zed · OpenCode · Qwen Code · Continue · Gemini.
Connect ChatGPT / OpenAI (MCP connector)
ChatGPT (and OpenAI GPT apps that support custom connectors) talk to AI Commander as a
custom MCP connector — a remote HTTPS endpoint. Works the same whether you are on ChatGPT,
GPT, or an OpenAI submodel such as Astra (gpt-6-astra).
On ChatGPT web, open Plugins, select the plus button, then Add custom MCP server. Enter a name (and optionally a description) and fill in Connection. Developer mode is no longer required (OpenAI help, checked 2026-10-21):
- URL:
https://aicommander.dev/mcp - Authentication: OAuth — AI Commander registers ChatGPT automatically, so there is nothing to paste; you complete a one-time browser sign-in.
- Tick I understand and want to continue, select Create as a plugin, install it, then type
@in a new chat and pick it.
Plans: running a command is a write action. Full MCP support, including write actions, is for ChatGPT Business and Enterprise/Edu on the web; Pro users can connect custom MCP servers with read/fetch permissions only, and custom MCP servers are not available on mobile. On other plans, use AI Commander from Codex or over REST.
For a code-only first hour without sign-in, use
https://aicommander.dev/mcp?anonymous=1 with no authentication.
No connector support? Drive a machine over plain REST
POST /api/v1/exec — see Chat apps and
REST API.
Full client matrix (ChatGPT, Codex, Claude Code, Cursor, Grok, REST): Connect your AI client.
OpenAI models, GPT, and Astra
AI Commander does not care which OpenAI model is answering — ChatGPT, GPT, or a submodel keyword like
Astra / gpt-6-astra (the same kind of label as Opus or Fable).
Your model stays the brain; this page is the harness that gives it your machines.
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 ChatGPT 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 |
|---|---|
| ChatGPT / OpenAI / GPT / Astra | Custom MCP connector or plain REST /api/v1/exec |
| Codex CLI | codex mcp add aicommander --url … → remote exec + jobs |
Grok / grok CLI | grok mcp add --transport http … → remote exec + jobs |
| Claude Code | MCP remote exec + jobs on your fleet |
| Cursor | npx @aicommander/mcp stdio bridge → remote exec + jobs |
FAQ
Next steps
Install the agent on a machine you control, add the ChatGPT custom connector, then ask for a real task on a remote box.