Skip to main content

​
How updates work

The Capsule daemon auto-updates itself. When a new release is published, the backend notifies every connected daemon over the existing SSE connection. The daemon downloads the new binary, verifies its SHA-256 checksum, replaces itself in place, and exits cleanly — systemd restarts it automatically with the new version. No manual action is required. capsule update is the manual fallback for cases where the daemon is not running, the auto-update did not apply, or you want to update immediately without waiting for the SSE signal.

​
Usage

The Capsule binary lives at /usr/local/bin/capsule, which is root-owned, so root access is required to replace it.

​
When to run this manually

​
What it does

sudo capsule update checks the Capsule release server for a newer version of the CLI. If one is available, it downloads the binary for your platform, verifies the SHA-256 checksum, and atomically replaces the current binary in place. If you are already on the latest version:
If an update is available:

​
After a manual update

Restart the service so the new binary takes effect:
This only applies when you ran sudo capsule update yourself. When the daemon auto-updates, it exits cleanly and systemd restarts it automatically — you do not need to do anything.

​
Notes

  • The update is atomic — if the download or checksum verification fails, the existing binary is left untouched
  • capsule update works even on a fresh install with no license key configured yet — checking for and downloading a new release doesn’t require authentication
  • Auto-update is safe during active backups — the running process stays in memory until it exits cleanly, so in-flight backups complete before the restart