Updates

Opsty keeps itself up to date, and it never restarts on its own: a restart would stop your dev servers, drop your ssh sessions and interrupt your agents. It downloads in the background and waits for you.

The tab strip with 0.4.1 ready beside Running, and the popover it opens: everything a restart would stop, and what happens to each one.

When it checks

About a minute after Opsty opens, then about once a day, and when your Mac wakes if the last check was a day or more ago, Opsty asks dl.opsty.dev whether there is a new version. If there is, it downloads it in the background, with no notification and nothing over your work. The first update after installing from the disk image downloads the whole app; later ones download only the parts that changed.

The check sends no account and no install ID. Downloading only the changed parts can show the server which version you had. The details are on the privacy page.

Opsty never offers an update your macOS can’t run. The file it checks says which macOS each version needs, and when yours is older, nothing is downloaded and Settings ▸ Advanced says why: 0.8.0 needs macOS 14 or later, so this Mac stays on 0.7.0. Copies from 0.4.0 to 0.6.0 hold back too, without saying why.

When an update is ready

A small 0.4.1 ready button appears in the tab strip, beside Running. Click it and a popover lists everything a restart would stop, and what happens to each:

  • a dev server: :5173 · started again;
  • Claude Code: resumes with --resume, in its own conversation; Codex: resumes with resume --last;
  • an agent in the middle of a turn: working · resumes with --resume, in amber, because the turn would be cut short;
  • an ssh session: reconnect offered;
  • anything on a server you marked as production: not brought back.
Restart and bring it back
Restarts into the new version now. When Opsty opens again, the Running when you left · earlier today sheet offers to start each one again; nothing starts until you say so. See Starting what was running.
Install when I quit
Puts the button away. The next time you quit Opsty, the update installs on the way out.
Later
Closes the popover. Quitting still installs the update. A stray Enter lands here, never on a restart.

After the restart, one message says Updated to 0.4.1, with What’s new for the changelog.

Checking by hand

Help ▸ Check for Updates… asks right away and opens Settings ▸ Advanced, where the answer stays. The menu item’s label follows what the updater is doing: Checking for Updates…, then Downloading 0.4.1…, and once the update is ready, Restart to Update to 0.4.1…, which opens the same popover. The launcher lists it too.

In Settings ▸ Advanced, the Opsty row shows your version and what the updater last did, such as Up to date, checked 14:02, with Check now (or Try again after a failure) and What’s new.

Turning the check off

Settings ▸ Privacy ▸ Check for updates turns the automatic check off, which is updates = "off" in config.toml. Check now and Check for Updates… still ask, because you did.

Opsty updates itself only from an Applications folder, yours or the Mac’s. Run from the disk image or from Downloads, Settings says so: Opsty updates itself only from the Applications folder. Move it there to get updates. Other messages are explained in Troubleshooting.