Compute & delivery1 min

Update the CLI

Industry standard: update the way you installed. Explicit only — never silent.

Rule: update the way you installed
Auto-update: never
Check only: sylphx update --check

Before you start

The Cloud CLI already installed
Knowing which channel installed it (curl, npm, pnpm, bun, Cargo or Homebrew)
For CI: a pinned version and an explicit upgrade step

No silent auto-update

The CLI never upgrades itself in the background. Agents and CI stay deterministic until you run an explicit update command.

Rule

Update using the same channel you used to install. That is how Codex, Homebrew, and most Linux tools expect package ownership to work.

By install channel

Property	Type	Description
`curl / standalone`	`command`	sylphx update # or re-run install-sylphx.sh
`npm`	`command`	npm install -g @sylphx/cli@latest
`pnpm`	`command`	pnpm add -g @sylphx/cli@latest
`bun`	`command`	bun add -g @sylphx/cli@latest
`Cargo`	`command`	cargo install sylphx-cli --locked --force
`Homebrew`	`command`	brew upgrade sylphx

sylphx update

sylphx update is the explicit entrypoint for upgrades. On a standalone install it refreshes the binary. On package-manager installs it should follow that manager (or tell you the exact command) — it must not silently overwrite a brew/npm/cargo install without an explicit force flag.

typescript

# Check only (no install)
sylphx update --check

# Upgrade (standalone installs)
sylphx update

# Machine-readable
sylphx update --check --json

Happy path is short

When you are already current you should see a single confirmation such as sylphx 0.2.6 is current. Details (package URLs, internal labels) belong on --check / --json, not the default success path.

If a prebuilt binary will not run

On older glibc hosts, prefer a host build:

typescript

cargo install sylphx-cli --locked --force

Was this page helpful?

Tell us what is missing, wrong, or unclear — this opens a real inbox.

Send feedback

Platform links