Updating

The CLI keeps itself current with no effort on your part.

It updates itself

By default the CLI checks for a newer release and updates in place — you normally never think about it. This is on for release builds and controlled by the --auto-update flag (default true).

To skip the check for a single run:

lily --no-update run "..."

To turn automatic updates off entirely, set an environment variable:

export LILY_NO_AUTO_UPDATE=1

Update now

To jump to the latest release immediately, re-run the installer — it always fetches the current build, verifies its checksum, and repoints your lily at it:

macOS / Linux:

curl -fsSL https://agent.pathvela.com/install.sh | sh

Windows:

irm https://agent.pathvela.com/install.ps1 | iex

Updating the background agent

If you run auto mode, the background server can move to a newer binary without dropping your work:

lily server reload

This starts a fresh server on the newest binary and hands the live sessions across. It's a no-op if nothing is running.

Check what you're running

lily --version   # prints e.g. "lily 0.1.35 (abc1234)"

lily bridge status also reports the running background version.

Removing it

  • Turn off auto mode: lily bridge uninstall.
  • Remove everything: delete ~/.lily/ (or your LILY_HOME directory).

Next