Skip to main content
reticle update moves the installed server forward and brings the app’s SDK with it.
No flags.

​
What it does, in order

  1. Ask the registry what is available.
  2. Compare by direction, not inequality. A registry version that merely differs is not a newer one, and the old check happily installed a downgrade.
  3. Nothing newer: log reticle_update with ok: false and message: "already on the latest version", then stop.
  4. Otherwise sync the app’s SDK first. reticle update used to swap only the CLI, so the command whose job is keeping an install current was itself a way to produce a version-skewed pair.
  5. Then apply the CLI update, which execs and exits. Your agent client restarts it.

​
What it prints

The SDK sync is best effort and non-fatal on purpose. This command gets run from wherever the human happens to be standing, which is often not an app at all.

​
Stuck on an older Windows release

Reticle 3.1.0 and older cannot apply this update on Windows and may fail with spawn EINVAL. Those releases run their own outdated updater, so retrying the command will not help. Run the installer directly from PowerShell instead:
This installs the current server without going through the old updater.

​
Exit codes

​
Worked example

Attaching to a running daemon is what a daemon is for, which means an upgrade does not take effect until that daemon dies. Run reticle stop afterwards if you need the new build serving immediately.
Last modified on August 15, 2026