Copilot CLI: Install, Update, Authenticate, and Launch

Use this on any platform when Node.js 22 or later is available.

Useful when your `~/.npmrc` sets `ignore-scripts=true`.

Good for testing features before they reach the stable channel.

A clean option for developer machines that already use Homebrew.

Lets you try upcoming releases from the Homebrew ecosystem.

Use this on Windows PowerShell v6 or later.

Useful when validating new features on Windows runners or laptops.

Best for macOS and Linux when you want a fast bootstrap without npm or Homebrew.

Equivalent to the curl installer when wget is your standard tool.

Useful in CI, sandboxes, or when testing a specific historical build.

If Copilot CLI is not already installed, `gh` can download and run it on supported platforms.

Good when you want GitHub CLI to handle installation and execution for you.

Use `--` so `gh` does not interpret flags intended for Copilot CLI itself.

Helpful when troubleshooting wrapper installs or forcing a clean download.

This is the default entry point for terminal-native Copilot sessions.

Use this outside the interactive slash-command flow when you want an explicit login step.

Useful when switching between GitHub.com and a supported enterprise host.

A clean reset when you need to swap users or re-run authentication.

Useful in support tickets, CI logs, and bug reports.

A common first fix when behavior differs from the latest docs or release notes.

Replace `commands` with another help topic such as `config` or `permissions`.