archgate upgrade

Upgrade Archgate to the latest version.

archgate upgrade

Checks GitHub Releases for the latest published version. If a newer version is available, the command auto-detects how Archgate was installed and runs the appropriate upgrade strategy. If already up-to-date, prints a message and exits.

Options

| Option | Description | | ----------- | ------------------------------------------ | | --plugins | Also update editor plugins after upgrading |

Install method detection

The upgrade command inspects the running binary path to determine the install method, then delegates to the matching strategy:

| Install method | Detection | Upgrade action | | --------------------------------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | Binary install (~/.archgate/bin/) | Binary lives inside ~/.archgate/bin/ | Downloads the latest binary from GitHub Releases and replaces the existing one | | Proto | Binary lives inside ~/.proto/tools/archgate/ | Runs proto install archgate latest --pin | | Local dev dependency | Binary lives inside node_modules/ | Detects the package manager from the nearest lockfile (bun, pnpm, yarn, or npm) and runs the appropriate add command (e.g. bun add -d archgate@latest) | | Global package manager | Binary lives in a global bin directory | Detects which package manager owns the global bin directory and runs its upgrade command (e.g. npm install -g archgate@latest) |

If no specific method is detected, the command falls back to npm install -g archgate@latest.

Plugin updates

After a successful upgrade, the CLI offers to update your editor plugins. In an interactive terminal, you get a confirmation prompt:

Archgate upgraded to 0.35.0 successfully.
? Would you like to update your editor plugins too? (Y/n)

The CLI auto-detects installed editors (Claude Code, Cursor, VS Code, Copilot CLI, opencode) and runs the plugin install for each selected editor. Plugin update failures are reported but do not affect the exit code — the CLI upgrade itself is already complete.

Use --plugins to skip the prompt and update all detected editors automatically:

archgate upgrade --plugins

Note

Plugin updates require authentication. If you are not logged in, the CLI prints a reminder to run archgate login first.

Examples

Upgrade the CLI:

archgate upgrade

Checking for latest Archgate release...
Upgrading 0.34.0 -> 0.35.0...
Archgate upgraded to 0.35.0 successfully.

Upgrade and update all editor plugins in one step:

archgate upgrade --plugins