Keep Junie.
Give it your machines.

AI Commander is not an alternative to JetBrains Junie, Claude Code, Codex, ChatGPT, Cursor, GitHub Copilot, Sourcegraph Cody, Grok, Gemini, Windsurf, Continue, Cline, Roo Code, Zed, OpenCode, Qwen Code, goose, Amp, Kilo Code, OpenHands, Amazon Q Developer, Augment Code, or Devin. 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.

Sibling harness pages: Cursor · GitHub Copilot · Cody · OpenHands · Amazon Q · Augment · Devin · Aider · Cline · Roo Code · Zed · OpenCode · Qwen Code · goose · Amp · Kilo Code · Continue · Windsurf · Claude Code · Grok · Codex · ChatGPT · Gemini · Cua Spaces · Kiro · Warp.

Connect Junie (remote MCP)

Junie, the coding agent by JetBrains (Junie CLI MCP docs · IDE MCP Settings), reads MCP servers from an mcp.json file. Per JetBrains’ docs, Junie CLI uses the same MCP JSON configuration as Junie in JetBrains IDEs, and remote servers are declared with a url (plus optional headers). Point it at AI Commander’s hosted MCP endpoint:

{
  "mcpServers": {
    "aicommander": {
      "url": "https://aicommander.dev/mcp"
    }
  }
}

Use ~/.junie/mcp/mcp.json for user scope (all projects) or .junie/mcp/mcp.json at the project root for project scope. Do not commit secrets: if you add an Authorization header with an API key, keep it in the user-scope file. In Junie CLI, the /mcp screen lists servers and their status; remote servers that need OAuth show Authorization required until you run Authorize and finish the browser sign-in. In a JetBrains IDE, open MCP Settings for Junie and edit the same JSON.

Prefer a local stdio bridge?

{
  "mcpServers": {
    "aicommander": {
      "command": "npx",
      "args": ["-y", "@aicommander/mcp"],
      "env": { "AICOMMANDER_SERVER": "https://aicommander.dev" }
    }
  }
}

Full client matrix (Junie, Augment, Devin, Claude Code, Codex, ChatGPT, Cursor, Copilot, Cody, Grok, Gemini, OpenCode, Qwen Code, goose, Amp, Kilo Code, Continue, Windsurf, Cline, Roo Code, Zed, OpenHands, Amazon Q, 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 a Bearer API key in headers. Menu names and options can differ between Junie versions — check the linked JetBrains docs for your build.

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, test suites, and training on the box that has the repo.
• Fleet list + GPU facts so Junie 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

FAQ