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. Reticle installs a registry version only when it is newer than the running version. It never installs an older one.
  3. Nothing newer: if this project’s SDK is older than the CLI, bring it up to the CLI’s version; then log reticle_update with ok: false and message: "already on the latest version", and stop.
  4. Otherwise, update the Reticle block in the agent rule files that already have one. Then update the app’s SDK first, so that the CLI and the SDK stay on the same version.
  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

A daemon that is already running keeps its own version. When no tab and no other agent is attached to it, your agent’s new MCP server stops it and starts the new version. When a tab or another agent is attached, the old daemon keeps running. Run reticle serve --restart to start the new version now.
Last modified on November 4, 2026