Updates

From a terminal

briglia upgrade

Add -y to skip the confirmation. briglia update is an alias.

From chat (Telegram or terminal)

Send /upgrade. Briglia downloads the release, verifies it, swaps its binary and resource bundle, restarts itself and confirms: “✅ Update x.y.z installed — Briglia restarted and is back online.” It refuses while a turn is running (/stop first) and when the install directory needs sudo — which is why the installer uses ~/.local/bin.

/restart re-executes Briglia without updating — the remote way to load configuration read at startup (mcp.json, skills).

What happens under the hood

1. Fetch the signed envelope from the latest GitHub Release and verify it against the key pinned in the binary (format, channel, signature, validity window).
2. Refuse if the sequence is below this install's trusted floor (rollback) or the version is older than the one running (a release is probably still publishing).
3. Stream the platform tarball to disk, bounded by the signed size, hashing as it goes; compare the SHA-256.
4. Extract, run bundle-check on the downloaded binary, then swap atomically in the install directory — with full rollback if any step fails.
5. Record the new sequence as the trusted floor, write a restart marker, re-exec.

Details and how to verify a release yourself: Security & signed releases.

Clients from before the rename

An Ada CLI ≤ 0.1.58 cannot update into Briglia: its updater is pinned to the old channel and refuses the new releases by design (a different channel name and location are exactly what the signature check rejects), telling you to reinstall. Run the install one-liner; it finishes with the explicit briglia migrate step, so nothing is lost. The same goes for the Ubuntu Touch app: the old ada.permaevidence package cannot update into briglia.permaevidence — install the new app, let it migrate, then remove the old one.

The Ubuntu Touch app

• The app itself: Settings → App updates → Check for updates, then Install update; close and reopen the app afterwards. “Update automatically when the app opens” is a switch, off by default. Installation goes through the system click installer and is verified against the click registry — a “success” that didn't land is reported as such.
• Briglia CLI on the phone: Dashboard → Update Briglia CLI. If Briglia runs as the service, it is restarted for you; if you started it by hand in a terminal, the app tells you to /restart it.
• Both channels are signed and rollback-protected exactly like briglia upgrade; the phone keeps its own trusted floor in ~/.config/briglia-ut/release_trust.json.