How an Outpost updates itself, what the Release or Beta channel changes, and what the status labels mean.
There is no manual update step. The Outpost checks at startup and every six hours after that whether a new version has been published for your channel. It only downloads one when the signed release list matches the version and the downloaded file has exactly the expected checksum. If either does not match, the running version stays in place.
Folders, release levels, permissions and the search index survive an update. A reinstall is never required, not even when you switch channels.
The channel applies to every paired Outpost in a workspace. You cannot switch it yourself — write to support@meingpt.com if your workspace should move to the other channel.
| Channel | What it is for |
|---|---|
| Release | The default. Versions that have been through the beta round. |
| Beta (earlier updates) | Signed builds earlier. Useful when you want fixes early or want to help verify them. |
Once we have switched the channel, it takes effect at the next check, so within six hours at the latest; no reinstall is needed. A machine that already runs a newer version is not downgraded — it waits until the channel catches up.
A version on your channel does not reach every device at once. MeinGPT releases it in waves, so that a fault does not hit the whole fleet. In the System tab you therefore see the rollout next to the version status:
The version status itself shows Up to date, Update available, Downloading update, Update ready to install or Checking for updates failed. On Windows the service installs the verified version by itself; where that does not apply, Install & restart appears.
If the new version does not come up cleanly, the Outpost returns to the previous one by itself and resumes serving with it. The slot reserved for this and what it holds is described under Where which data lives.
If a device stays on Checking for updates failed for days, a blocked outbound path is one possible cause among several — a manifest signature that fails verification or an update the install gate refuses show the same status. Run the checklist under When something breaks; if that does not explain it, write to support@meingpt.com with the device name and when it started.