Updates and versions
A release build checks ten seconds after a launch and then every hour, so a window that is never closed still learns of a release within the hour. Everything downloaded is signature checked before it is installed.
How a new version arrives
A new version gets ready by itself. On macOS it is downloaded, checked and installed in the background while you keep working; on Windows it is downloaded and checked, and the installing itself takes the few seconds of the restart, because Windows cannot replace a program that is running. While that happens an "UPDATE v0.6 · GETTING READY" button sits in the toolbar, beside the rail button, and the status bar says the same.
The window and the button

Then a window of the system's own says once, in one sentence, that a new version is installed on this computer and a restart updates (the release note stays on the release page and in the email; the founder's wish, 2026-09-22), with "Restart now" and "Later".
- Restart now closes Kestrel Browser and opens it updated.
- Later keeps an "UPDATE v0.6 · RESTART" button in the toolbar, beside the rail button, where the eye is; it brings the same window back, and the window does not return by itself for that version until the next launch. The button changes colour with the days the version has waited, the way Chrome's does: green at first, orange from the fourth day, red from the seventh. The status bar repeats the line while it is turned on.
On macOS a quit and a fresh start do the same as the button.
When automatic updates are off
Settings > Updates and about > "Update automatically" turns all of it off: nothing is checked until you press "Check now" or the menu's "Check for Updates", and a new version is then offered the older way, "Install now" or "Skip for now", one answer installing and restarting.
The same older offer appears when Kestrel Browser sits in a folder it may not change by itself (the Applications folder under a standard account): installing then needs your password, so it waits for your click.
If the engine stops
The pages are drawn by the system's browser engine (WebView2 on Windows, WebKit on macOS), which runs each page in a process of its own. When a page's process stops, Kestrel Browser reloads the page and the status bar says so, naming the site; a page whose process stops a third time in ten minutes, after two reloads, is shown "This page stopped working." with "Try again" and "Close tab" instead, because a page that keeps stopping is usually out of memory or hitting a driver problem. When the process behind Kestrel Browser's own toolbar and tabs stops, the toolbar is redrawn with your tabs, your wallet and the update button as they were (what you had typed in the rail is gone). When the whole engine stops at once (Windows), or the toolbar keeps stopping (both systems), Kestrel Browser closes and opens again by itself with your tabs restored, whatever "On startup" is set to, and says so; the wallet is locked again, armed orders wait for your unlock as after any restart, and cookies set to "Clear on quit" are kept through this restart and cleared at your next quit. A page the engine reports as not answering is not reloaded by itself: the reload button and Ctrl+R are yours, and they ask the engine to reload, so they work on a page that no longer runs its own scripts.
Checking by hand
The menu's "Check for Updates" and "Check now" always answer, with the window, the offer or a line saying this build is up to date.
Where the version shows
The version shows in the title bar chip (v0.4), in Settings > "This build" with the system details and the install id, and at the top of the report page. Versions people see have one dot until 1.0.
This guide
This guide lives at kestrelbrowser.com/docs and says at the top which version it was checked against; the menu's User Guide, the start page's User guide and Settings > Updates and about open it in a tab.