App and Updates
Background update checks with Minisign (Ed25519) signature verification, launch at login, runtime capabilities, and when to restart.
The app checks for updates in the background: once a few seconds after startup, then every 15 minutes. "Settings → App update" includes an "Automatically download updates" toggle (enabled by default): when enabled, new versions download quietly in the background; when turned off, Klaus only announces a new version and waits until you click "Download update". Available, downloading, and ready-to-install updates stay in the compact card above the bottom-left sidebar footer instead of opening a centered modal over your work; the centered installation dialog appears only when you click "Restart to update". There are three ways to check manually: the "Check for updates" button on "Settings → App update", "Klaus → Check for Updates…" in the macOS app menu, or asking Klaus to check. When updates are unavailable (development build, custom data directory, and so on), the reason is shown.
The "Settings → App update" page is the one place for everything version-related: the current version number, manual check/download/install controls, the "Automatically download updates" toggle, and the entry to open the release notes. It reads the same update state as the sidebar update card, so you will never see one place reporting a new version while another says there is none.
- Update packages carry a Minisign (Ed25519) signature. The package is downloaded into a private cache directory only you can read and write (
~/.klaus/electron/updates/), verified as soon as the download finishes, and made read-only; when you confirm the install, Klaus fetches the update feed again to check the package is still the current signed release and re-verifies the cached file before handing it to the installer. A tampered package, or a release that has since been withdrawn, cannot be installed. - Once you confirm the install, Klaus itself swaps in the package and restarts. If the swap fails, it does not restart: the currently running app stays untouched and you are told why.
- Self-built or development versions have no signed package and no update source, so they report "updates not supported" and refuse to install, rather than pretending to check. If clicking "Check for updates" seems to do nothing, look here first.
Other app-level matters:
- Launch at login: you can have Klaus start when you log in to the system (useful for guarding scheduled tasks and channel messages — if the app is not running, nobody is there to pick up messages).
- Current version: always shown at the bottom of the settings sidebar (consistent across platforms); on macOS it also appears in the system panel at "Klaus → About Klaus" in the menu bar.
- Runtime capabilities: to find out whether a capability is available on this machine, just ask Klaus — it answers from the local runtime capability snapshot.
- Restart: newly granted system permissions and some engine configuration changes take effect only after a restart. If you ask Klaus to restart on your behalf, it checks with you first (a restart interrupts work in progress).
- Looking at the current window: Klaus can take a screenshot of its own window and read the image, so when you say "look at this page of mine" it really can see it instead of guessing.