How the desktop terminal updates itself — signed builds, checking your version, and what happens on a failed update.
The desktop terminal keeps itself current. It checks a small release manifest — shortly after launch, quietly in the background, and any time you ask it to — compares the published version against the one you're running, and offers the update when a newer build exists. The background check only speaks up when there is actually something new; otherwise it stays silent.
Nothing downloads or installs without you choosing it. When an update is available you get a prompt with the new version number and its release notes, and two options: Download or Later. Updates apply in place — no hunting for a fresh download, no reinstalling, no losing your workspaces.
Occasionally a release is marked required — for example a critical fix. The prompt says so explicitly, and Later becomes Quit: you take the update or close the terminal.
Every public build is code-signed. Before the updater applies anything, it verifies what it downloaded:
The updater also refuses outright to install a release that ships without an integrity checksum. I'd rather a release be a day late than have the terminal apply a single byte it can't verify — if any check fails, you stay on the version you're running and the terminal tells you what happened.
Help ▸ About Sharpnel Desktop | Shows the exact version you're running, plus build identifiers — useful when you're talking to support. |
Help ▸ Check for Updates… | Runs a check right now and always tells you the outcome: a new version is available, you're on the latest version, or the check couldn't reach the release manifest. |
The manual check reports every outcome — including "You're on the latest version" — so you can confirm you're current at any time. If the check fails (for example, you're offline), the terminal says so and keeps running normally; the background check simply stays quiet and tries again next launch.
Download / Later.Download and a progress dialog walks through Downloading, then Verifying — the checksum and signature checks above.The whole thing is designed to be a sub-minute interruption, not an evening project.
A failed update never leaves you with a broken terminal. The updater stages the new build alongside the version you're running, and only swaps once the download has fully verified:
Help ▸ Check for Updates…..old file) and is cleaned up automatically on the next launch.Not on Pro yet? Upgrade to Pro — the desktop terminal is included.