Upgrade

LoomBrain enforces a minimum CLI version. Older versions may receive warnings or be blocked outright. Keep lb up to date to avoid interruptions.

How to upgrade

npm

npm update -g @loombrain/cli

Homebrew

brew upgrade lb

Check your current version:

lb --version

Version enforcement layers

The CLI and API coordinate through three layers of version enforcement, in increasing severity.

1. Proactive notification (startup check)

On every invocation, lb checks the npm registry for a newer version. The result is cached for 24 hours so it does not slow repeated invocations.

When a newer version is available, the notice appears below command output:

Update available: 1.2.0 → 1.4.0
Run: npm update -g @loombrain/cli

This check is advisory. Commands still run.

2. Recommended version (API header)

Every API response may include an X-Recommended-CLI-Version header. When the CLI detects that its version is below the recommended version, it prints a warning once per session:

Warning: CLI version 1.2.0 is below the recommended version 1.3.0.
Run: npm update -g @loombrain/cli

Commands still run. This warning persists until you upgrade.

3. Hard block (HTTP 426)

The API returns HTTP 426 Upgrade Required when the CLI version is below MIN_CLI_VERSION — a hard floor enforced server-side. The CLI detects 426, prints an error, and exits without completing the command:

Error: Your CLI version (1.0.0) is no longer supported.
Minimum required version: 1.2.0

Upgrade now:
  npm update -g @loombrain/cli
  brew upgrade lb

Docs: https://docs.loombrain.com/cli/upgrade

The only resolution is to upgrade.

How the version is sent

lb sends its version on every API request via the X-CLI-Version request header. The API uses this value for both the recommended-version warning and the 426 hard block check.

Suppressing notifications

To suppress the proactive startup notification (layer 1 only):

export NO_UPDATE_NOTIFIER=1

Notifications are also suppressed automatically when CI=true is set or when stdout is not a TTY. The recommended-version warning (layer 2) and the 426 hard block (layer 3) cannot be suppressed — they require an upgrade.