Update krites¶
Keep the macOS app current from inside the studio — no terminal, no
re-downloading the .dmg. krites updates in place to the latest signed release
and restarts itself.
Check for and apply an update¶
- Open the studio (double-click Krites, or
krites studio). - Click the ⚙ gear in the top bar to open the settings panel.
- In the Updates section you'll see the version you're running and a Check for updates button. Click it.
- If you're already on the latest release, it says so and you're done.
- If a newer release exists, krites downloads the new signed build, verifies it, replaces itself, and shows a full-screen "Updating krites…" overlay while it restarts. When the new version answers, the page reloads onto the upgraded studio automatically.
Your shoots, verdicts and edits are untouched — updating only replaces the program, and your config is migrated on restart.
macOS app only
In-place self-update is a feature of the packaged macOS app (it's the build
that ships as a signed .dmg and knows how to replace itself). A CLI install
(krites from a tar.gz) updates with krites update instead, or by
re-downloading the archive.
If the restart doesn't come back
The overlay waits for the restarted studio and, if it doesn't answer within a couple of minutes, tells you to reopen Krites. Just double-click Krites again — the launcher reopens the studio (now on the new version).
What "update" actually does¶
- Reads the release feed (
phpboyscout/kritesGitLab Releases), the same source thekrites updateCLI uses. - Downloads the newer signed, notarized build and verifies its signature before applying — a failed download/verify leaves your running app untouched.
- Replaces the on-disk binary and re-execs itself on the same port, so the studio comes back where it was.
krites never auto-updates: a periodic check may notify you that a new version is available, but applying it is always your choice.