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.
- 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 · 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:
Persist the extension with interactive configure, or edit ~/.config/goose/config.yaml
(goose uses uri and type: streamable_http — not url):
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 |
How goose handles MCP servers
- In goose an MCP server is an extension. Remote extensions use
type: streamable_httpwith auriin~/.config/goose/config.yaml, and each one has its owntimeoutin seconds (the docs use 300). goose session --with-streamable-http-extension URLloads an extension for that session only. Nothing is written to the config file.- Extensions can be installed from a deeplink of the form
goose://extension?url=…&type=streamable_http. - OAuth uses dynamic registration or a client ID metadata document, or a pre-registered
client_id. The callback listens on 127.0.0.1 on a random port (GOOSE_OAUTH_CALLBACK_PORTfixes it). - goose checks extensions against known malware before turning them on.
- Changes to default extensions apply to new sessions. Extensions enabled mid-session with
/extensionlast only until that session ends.
Checked against goose docs: Using extensions in November 2026. Client behaviour changes between releases; the official docs win if they disagree.
A workflow that suits goose
goose works autonomously by default. That suits jobs you start and walk away from, as long as you set the permission mode on purpose.
- Add the
aicommanderextension with a generous timeout, and pick a permission mode that asks before tools run, at least until you trust the flow. - Write a short prompt you can reuse: "On the NAS, check disk usage and SMART status, then start a scrub as a background job if anything looks wrong."
- goose calls
remote_execfor the quick checks andremote_job_startfor the scrub. You come back later and ask forremote_job_logs.
Limits and gotchas in goose
- In the default autonomous mode, goose can call
remote_execwithout asking. Pick the permission mode deliberately before connecting machines you care about. - An extension added with
--with-streamable-http-extensionis gone in the next session. Add it to the config for permanent use. - If the OAuth callback is blocked by a firewall, pin
GOOSE_OAUTH_CALLBACK_PORTto a port you have allowed.
FAQ
remote_exec./extension or the --with-streamable-http-extension flag. Add it as a regular extension in config.yaml.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.