Minions Mission Control

Quick Start

Prerequisites: Node.js 22.5+, Git, Azure CLI, and at least one agent runtime — install Claude Code or GitHub Copilot CLI separately. Nothing needs to be cloned: the installer pulls @opg-microsoft/minions straight from the ISS ProjectFeed-ISS Azure Artifacts feed.

Download the installer for your platform

Two ways to run the same install — pick the one that matches your machine.

• Windows

  PowerShell

  Download install-minions.ps1

  Run it from any directory — edit the path if you saved it elsewhere:

  powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\Downloads\install-minions.ps1"

• macOS or Linux

  bash / zsh

  Download install-minions.sh

  Run it from your download folder:

  bash ./install-minions.sh

Running the downloaded installer is the whole install — there is no separate sign-in step. It reuses an Azure CLI session you already have without prompting; if you have none it signs you in once itself with az login --allow-no-subscriptions, then retries the token exactly once. A headless or automated run never hangs on a prompt: it stops immediately and prints that command for you to run in a real terminal. The short-lived Azure DevOps token it gets is used only in a throwaway npm config it deletes on exit, and it never creates or stores a PAT. It verifies feed read access before it changes anything on your machine, then stages the verified version of @opg-microsoft/minions into that same throwaway folder and hands the rest to the canonical installer that ships inside the package. Nothing is installed globally until that installer owns the order: it backs up your state, removes any earlier public-npm install before installing the internal one, then runs minions init and a health-verified restart. It is idempotent: re-run it any time to upgrade.

Both installers install the newest published version by default. To go back to a known-good older build, pin an exact version — -Version 1.2.3 on Windows, --version 1.2.3 on macOS or Linux, or MINIONS_INSTALL_VERSION=1.2.3 in the environment, with the flag winning over the environment. A pin that is not an exact published version is rejected before the installer requests a token, creates its staging folder, or downloads anything, and the pinned version is the one that is staged and handed to the canonical installer — the two can never split. Each run also prints its launcher revision as its first line (==> Minions launcher install-minions.ps1 sha256:…); quote that line in a bug report so a stale copy sitting in your downloads folder is obvious.

After the installer finishes

# Bootstrap ~/.minions/ and scan/link repositories
minions init

# Or add a specific project later
minions add ~/my-project

# Start engine + dashboard, then open http://localhost:7331
minions restart --open
minions dash

# Give your first task
minions work "Explore the codebase and document the architecture"

# Useful operations
minions status
minions doctor
minions config set-cli copilot --model gpt-5.4

# Update to latest
minions update

Minions is published as @opg-microsoft/minions to the internal ProjectFeed-ISS Azure Artifacts feed — it is not published to public npm. Installing needs an Azure identity and Azure Artifacts read permission on ProjectFeed-ISS, because the feed is private to the organization. You do not run az login yourself: the installer uses the Azure CLI session you already have, and signs you in once with az login --allow-no-subscriptions only if there is none. If your identity is signed in but not authorized, it says so instead of sending you back through a sign-in that cannot help. The installer's npm view check then proves feed access before anything on your machine changes, so a missing permission fails safely; request feed access from the ISS feed owners and re-run.