Keep goose.
Give it your machines.

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

Positioning in one line: goose 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 · goose · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini.

Connect goose (MCP Streamable HTTP)

goose (docs) is Block’s open-source AI agent with native remote MCP extensions over Streamable HTTP (SSE transport was removed — use Streamable HTTP). Point it at AI Commander’s hosted MCP endpoint:

goose CLI — one session

$ goose session --with-streamable-http-extension "https://aicommander.dev/mcp"

Persist the extension with interactive configure, or edit ~/.config/goose/config.yaml (goose uses uri and type: streamable_http — not url):

goose configure

$ goose configure # Add Extension → Remote Extension (Streamable HTTP) # Name: aicommander # URI: https://aicommander.dev/mcp

~/.config/goose/config.yaml

extensions: aicommander: enabled: true type: streamable_http name: aicommander description: Remote machines via AI Commander uri: "https://aicommander.dev/mcp" timeout: 300

Full client matrix (goose, Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, OpenCode, Qwen Code, Continue, Windsurf, Cline, Roo Code, Zed, REST): Connect your AI client. Extension docs: Using extensions · CLI commands.

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 URI. For optional account features (saved aliases), add a header in config: headers: { Authorization: "Bearer <your-key>" } (or enter the same header when prompted by goose configure).

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 goose 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
goose	`goose session --with-streamable-http-extension "https://aicommander.dev/mcp"`
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

Is AI Commander an alternative to goose?

No. AI Commander is a remote-machine harness. You keep goose (or Claude Code, Codex, ChatGPT, Cursor, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen 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 goose to AI Commander?

Add AI Commander as a Remote Extension (Streamable HTTP). Quick session: goose session --with-streamable-http-extension "https://aicommander.dev/mcp". Or run goose configure → Add Extension → Remote Extension (Streamable HTTP) and enter that URI. Or add type: streamable_http with uri: "https://aicommander.dev/mcp" under extensions in ~/.config/goose/config.yaml. First connect may open a one-time browser sign-in (OAuth Dynamic Client Registration). Use ?anonymous=1 for a code-only first hour. Optional: set headers Authorization: Bearer <your-key> for account aliases. See /howto/ for the full matrix.

How is this different from goose running locally only?

Local goose is the brain in your terminal or Desktop. AI Commander adds hands on servers, GPU rigs, NAS, and other laptops you own — outbound-only, no inbound ports, no exposed SSH — so goose can run shell, detached jobs, and file transfer on those machines over MCP.

Next steps

Install the agent on a machine you control, connect goose via Streamable HTTP to https://aicommander.dev/mcp, then ask for a real task on a remote box.

Install the agent Setup guides Remote coding agents

Keep goose.Give it your machines.