A beta can give you a new feature before it is ready for your everyday work. When you want to return to the stable release, OGAD (Off Grid AI Desktop) has an update-channel control. You do not have to delete your chats to change channels.
Download OGAD | Desktop releases
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
Changing the app version and restoring its data are separate operations. A portable backup protects the supported workspace content; it does not guarantee that every beta database change can be reversed.
Save the work you need first
Finish active generation and transfers. Open Settings → Backup & restore → Create backup and save the ZIP outside the app's data folder. Check that the export reports success and the file exists.
The portable backup includes chats, projects, project instructions and knowledge files. It is not a full copy of models, Vault, screen history or every setting. Keep any other important material through its own supported export. If you have a backup made before installing the beta, keep it as well as this current export.
Do not uninstall the app and remove its data as a first troubleshooting step.
Select the stable channel
- Open Settings → Software update.
- Turn Nightly builds off. This selects the stable channel.
- Let the update check finish. Use Check for updates if you need to check again.
- Review the offered version. If it needs a manual download, use the displayed Download control.
- Wait for the download to finish, save open work, and restart when the update banner offers it.
- Check the installed version in Settings and open an existing chat and project before resuming important work.
The explicit channel change permits moving to a numerically lower stable version. Routine checks do not silently downgrade a beta. These controls are present in OGAD 0.0.51 and the 0.0.52 beta series.
Make a short return-to-work check after the restart
Use an existing project you can inspect. Open one saved conversation, confirm that its recent messages are present and check that the project's important documents are listed. Then select a compatible local model and ask one small question.
If you use a Pro workflow, check that particular workflow separately. A successful chat reply does not prove that a saved meeting, a vault or every beta feature behaves the same in the stable version. A beta-only control may no longer appear after the downgrade.
Keep the current backup and any pre-beta backup until you are satisfied with the result. Do not replace both with a new export before checking what the stable app can read.
Identify which part failed before trying another restore
A failed update download is a connection or updater problem. An installed version that starts but cannot read a record is a data-compatibility problem. A missing beta-only control can be an expected feature difference.
Record the version you left, the version now installed and the exact message shown. That gives you a useful support report and avoids repeated changes with no record of what happened.
Portable restore adds supported missing records; it is not a time machine for the entire app profile. If you need a full return to a pre-beta state, keep the relevant backup intact and use a verified recovery route for that data. Do not delete the only copy of a record while trying to make a downgrade look clean.
What if no stable update appears?
The update check needs internet access. Read the status shown in Software update; do not treat a failed check as proof that no release exists. Confirm that Nightly builds is off and compare the offered version with the public release page.
An app-version change does not prove that an older build can read every record created by a newer beta. If the stable app cannot use the data, keep the original backup and report the version pair and error. Do not overwrite your only backup while trying repeated restores.
Choose backup adds missing supported workspace records; it is not a whole-profile rollback or a way to undo every changed record.
Get OGAD, save a portable backup, and use the channel control to return to the stable release when it suits your work.
Top comments (0)