Skip to main content

Update LightNow CLI and Proxy

The LightNow CLI checks and updates both local LightNow components. The Local Proxy reports its version and update status, but never invokes a package manager or delays MCP startup for a release check.

Check before changing anything​

Show installed and available versions
lightnow update --check

For automation, request the same result as JSON:

lightnow update --check --json

The command exits successfully when the check completes, including when an update is available. Network, catalog, or validation failures return a non-zero exit code.

Apply updates​

Confirm and update CLI plus Proxy
lightnow update

Use --yes only when the update is already approved:

lightnow update --yes

Managed updates support:

InstallerCommands managed by LightNow
HomebrewTap refresh followed by formula upgrade
pipxIsolated package upgrade
uvIsolated tool upgrade

LightNow does not modify editable installs, plain pip environments, unknown virtual environments, or repository checkouts. The result identifies these as unsupported and leaves them untouched; update them with the installation method that owns that environment.

Automatic notices​

Interactive terminal commands read a private cache under ~/.lightnow/. At most once per day, the CLI refreshes that cache in a detached helper and shows a short notice on a later invocation when an update is ready. Checks are skipped for non-interactive output, CI, and JSON workflows.

Disable automatic notices without disabling the explicit update command:

export LIGHTNOW_NO_UPDATE_CHECK=1

Verify and restart​

lightnow --version
lightnow-proxy --version
lightnow update --check

The updated CLI is active on the next invocation. Restart MCP clients after a Proxy update so they launch the new executable. If the update fails, preserve the JSON result and continue with Debug LightNow Proxy.