Notifications and updates
A desktop notification fires when a thread finishes or needs a decision from you, never while the window is focused, so parallel runs do not turn into a stream of pings while you watch them. For work that ran while you were not watching, the morning digest collects it into one summary: what ran, what it cost, and what changed.
A desktop notification fires when a thread finishes or needs a decision from you, never while the window is focused, so parallel runs do not turn into a stream of pings while you watch them.
For work that ran while you were not watching, the morning digest collects it into one summary: what ran, what it cost, and what changed. A waiting update shows next to the sidebar Settings button as a button that installs it and relaunches, so you do not have to open Settings, or GitHub, to act on one.
Updates come from plain GitHub releases on two channels: prod follows the newest normal release, nightly the newest prerelease, and a nightly install never migrates itself onto prod. Nightly ships as Solenta Nightly with its own bundle identifier, so both channels can sit side by side; they share one user-data directory. Checking is automatic; installing is not. Solenta downloads only when you click, verifies the archive against the sha256 digest GitHub stamps on the asset, then swaps the bundle in place on macOS. Windows and Linux stage the new tree and swap it in when you Restart. Builds from a dev tree carry no channel stamp and never self-update.