Data folder recovery (your data looks gone after an update)
What happens when the app's data folder is renamed between versions, and what to do if you ever open the app and your projects and sessions appear to be gone. Covers where the folder lives on each platform, how the move decides between two real folders, and the Mac sign-in key that has to be migrated with it.
On this page
What it is
Omniscio keeps everything — sessions, projects, hubs, plugins, automations, settings — in one
data folder on your computer. When the app's folder name changes (it changed from
agent-mission-control to omniscio in the 0.1.103 update), the first launch of the new version
moves your existing folder onto the new name so nothing is lost.
If it cannot do that safely, Omniscio now asks you instead of quietly starting an empty profile.
Where to find it
The folder itself is not something the app shows you a button for unless you go looking: Settings → System → Data Folder prints the exact path and has an Open Data Folder button that takes you straight there in your file browser. When the move needs your input it comes to you instead — a dialog on launch, or a notice in your inbox if a sign-in ever stops being confirmable.
Where the folder lives
- macOS:
~/Library/Application Support/omniscio - Windows:
%APPDATA%\omniscio - Linux:
~/.config/omniscio
Settings → System → Data Folder shows the exact path and has an Open Data Folder button.
How it behaves
How the move decides
On launch, before anything else opens, Omniscio checks whether a folder with the previous name still holds a database:
- The new folder does not exist yet → your old folder is renamed to the new name. Done.
- The new folder exists but was never really used — it holds no database, or a small database (under 5 MB) with zero sessions that no running copy of Omniscio owns (a leftover from a crashed first start or a developer run) → that leftover is set aside as a timestamped sibling (nothing is deleted) and your old folder is moved into place. A database that reports zero sessions but is larger than that, or whose size cannot be read, is treated as real data and never moved.
- Both folders hold real data → Omniscio shows a dialog: "Your previous Omniscio data was
found", naming both folders.
- Use my previous data and restart — the app restarts, sets the current folder aside (kept, not deleted) and moves your previous data into place. You are back where you were.
- Keep this profile — the app continues with the current folder and remembers your choice, so it does not ask again.
An older installed copy on the same computer
Current versions keep each account's data in its own folder inside the data folder
(omniscio\profiles\<your account>). A copy of Omniscio installed before that change only knows the
data folder itself, so if you open it after a newer version has moved your data, it finds the
folder empty and quietly starts a brand-new install there — with its own setup screens and an empty
session list. Your real data is untouched in your account's folder.
The newer version leaves that leftover exactly where it is: once an account is active it never treats the data folder as an unfinished move, so it does not merge the older copy's files into your account and does not delete them. When you start Omniscio from its source code, the launch check also lets the launch go ahead instead of stopping with "Database migration is split". It does that when your account's folder already has its own database and the leftover database was created later and is not larger (or only the older copy's settings file is left). When it cannot tell — for example the file creation times cannot be read — it still stops and asks you to sort the two out, so a real unfinished move is never skipped.
Two copies cannot run on the same data folder at the same time: the second one to start says the folder is in use. Close the other copy, or update or uninstall the older installed copy so it moves onto your account's folder too.
If you already see an empty app
Do not use "Restore from backup" for this — that list only shows backups of the profile you are
currently in (the empty one). Quit Omniscio, then in the data-folder location above rename the
current omniscio folder to something like omniscio.old, rename your previous folder
(agent-mission-control) to omniscio, and start the app. Your previous folder still has its own
backups/ inside it.
Saved sign-ins after the move (Mac)
On a Mac, the key that protects your saved sign-ins — your accounts, connected services and the
Google sign-in setup — lives in your login Keychain under the app's old name. Right after the
move, Omniscio checks whether it can still open them. If it cannot, it asks "Restore your saved
sign-ins?" before anything else loads: choose Restore and restart, allow the macOS
permission prompt (sometimes two), and Omniscio restarts with everything readable again. The key
it replaces is kept in your Keychain under omniscio Safe Storage (before restore …), so nothing
is lost. Choosing Not now means signing in to each account again, and the question is not
asked again once you have answered (a copy that fails is retried on the next start, at most three
times). This particular question is Mac-only — Windows has no Keychain item to copy — but the
symptom it is about is not, and Windows has its own answer to it; see If Omniscio says the
encryption key has changed below.
If your sign-in broke and you did not notice. A half-restored sign-in is the awkward case: your account id is stored in plain text, so Omniscio keeps showing you as signed in, while the saved credential it needs to confirm your account is gone. After a week of not being able to confirm it, anything tied to your plan quietly starts behaving as if you were on the free plan — higher limits, cloud features, and publishing a share without the "Made with Omniscio" badge. Omniscio now tells you instead of going quiet: you get one inbox notice, "Omniscio can’t confirm your account", with a button that takes you to Accounts to sign in again. It appears as soon as the app checks (on launch or reconnect), not hours later; it repeats at most once a day rather than every few hours; and it clears itself the moment your account is confirmed again. You are never signed out or locked out by it — if you are simply offline, nothing changes and no notice appears.
If you skipped it and want it back later: quit Omniscio, open Keychain Access, copy the
password of the agent-mission-control Safe Storage item into the omniscio Safe Storage item
(create it if it is missing), delete the file keyring-migration.json inside the data folder, and
start the app. If Omniscio still reports that it cannot read your sign-ins after a restore, the
key it copied was not the right one — the same manual copy fixes it.
If Omniscio says the encryption key has changed
Every saved secret is sealed with a key that lives in the data folder itself — in Local State on
Windows, in the login Keychain on a Mac. If that file is ever replaced (a profile reset, moving the
folder about by hand, restoring a backup of part of it), the key changes and anything sealed with
the old one can no longer be opened. Windows' own protection is unaffected: this is not a fault of
the machine, and it is not something a restart repairs.
You will notice it as one or more cards: "A saved Omniscio secret can't be read", "Your saved API key can't be read", or "Backup Mirror has stopped". Omniscio now tells the two situations apart and says which one you are in. The card that says the key has changed means it will not fix itself — but on Windows, Omniscio can usually put them back for you.
"Restore your saved secrets?" The key those secrets were sealed with is normally still on the
computer, in the folder your data was moved to when the app's folder name changed or the folder was
set aside. Omniscio looks at the saved secrets it cannot read, and when it finds that older key and
can prove it opens every one of them, it offers to put them back: one click, no signing in,
nothing re-entered, and Omniscio restarts itself when it is done. It writes nothing until you click;
it repairs only the secrets that cannot be read and leaves the ones that still work exactly as
they are, so anything you have signed in to again since the change is never touched; and it keeps the
file it replaced beside the original (config.json.pre-reseal-…), so nothing is lost either way.
Once those secrets can be read again, local backups resume being encrypted too, because the
backup key is restored at the same time.
If that offer does not appear — for instance if that older folder has since been deleted, or if a secret that cannot be read is one that older key cannot open either — each thing has its own remedy:
- Push notifications come back by themselves the next time one is sent — each phone or browser that was subscribed has to connect again.
- The Backup Mirror keeps working once you re-enter the same passphrase in Settings → Backup & Restore → Backup Mirror. Entering a new one would make the archives already in your backup folder unreadable, so use the one you chose.
- An API key, a sign-in, or a connected service has to be entered or connected once more from its own page in Settings.
- Local backups are unaffected going forward. Omniscio keeps the previous backup key aside
(
backup-encryption.key.before-…) and writes a fresh one, so new backups are encrypted again rather than being written unprotected.
Nothing is deleted in any of this: the unreadable values are kept exactly as they are, so a card clears itself the moment its secret is supplied again.
When a folder move leaves stored paths behind
An install that predates per-account profiles has its data moved into profiles/<account>/ once. The
move itself is a rename, so it does not touch the absolute paths already stored inside that data
that point at the old location. Three rules make that safe:
- The move finishes. A root entry whose profile copy already exists can never be moved, so it is reported and left rather than counted as outstanding work. Only a move that actually failed keeps the migration's resume marker, and a root that already names an active account is never treated as an un-migrated one.
logsstays at the root. The liveness tapes are read from the root by other programs that do not know which account is signed in, so that folder is machine-level, besidemodels/andwake-word-models/, and is never carried into a profile.- A profile is never migrated into itself. The mover refuses any folder that is itself a profile,
so a boot that hands the profile folder in as the data folder cannot create
profiles/<account>/profiles/<account>and deepen it again on the next restart. - Stored paths are repaired once. A path is rewritten only when its old location is gone AND the
same relative path exists under the profile. A reference that still resolves is left exactly as it
is, which is what keeps references to the root
logsfolder working. The repair runs once per account, only for jobs this computer runs, and it retries next launch if any write missed.
A path written by hand inside a script or a prompt that names a moved folder is not repaired. Only the paths the app itself stores are.
Related
If you did end up on a new, empty profile and want to check what the app decided and when, the startup trace records which folder was chosen on each launch. The ordinary backup and restore surface — which is a different thing from this folder move, and will not help with it — is on the automatic backups and restore page. A sign-in that stopped being confirmable, and what the app now does about it, is covered on Plan & Usage.
- Startup trace — the launch log that records which folder was chosen
(
[Startup] dataDir=…) and anySPLIT DATA DIR DETECTEDline. - Automatic backups and restore
Last verified 2026-11-18