Off-machine backup prompt (a backup that survives losing the computer)
A default install's only backup lives on the same disk as the database, so losing the machine loses everything. This is the gentle, consent-first prompt that invites a new user to set up a backup that lives somewhere else — what it says, when it appears, and why it never turns a backup on for you.
On this page
What it is
STATUS: the BANNER is off; the inbox alert is back ON. A brand-new user should not be greeted by a data-loss warning, so the
<OffMachineBackupOffer/>banner mount was removed fromAppBanners.tsx(owner, 2026-08-18) and is still absent. The component + its routing stay in-tree; if backup nudging returns it will be an inbox notification, not a banner.The matching "Backups are on the same disk" inbox alert was RE-ENABLED on 2026-08-30 (audit B1):
BACKUP_COLOCATION_ALERT_DISABLEDinbackup-failure-alerts.tsis nowfalse, and brand-new users are instead protected by the new-user alert hold (new-user-alert-hold.tsholds thebackup-colocatedkey through onboarding and for 24h after setup). So the risk IS surfaced today — as a persistent inbox card carrying a one-click Open Backup settings action, plus the in-panel warning described under Where you see it.
What it is — A gentle
A gentle, one-time prompt that invites a new user to set up a backup that lives off this computer. It exists because a default Omniscio install keeps no backup that survives losing the machine: the only backup that is on by default (the local auto-backup ring) writes to the same disk as the database, so one disk failure, theft, or ransomware event destroys every project, session, and conversation with no copy anywhere else. Every off-machine copy (the cloud-folder Backup Mirror, Cross-Device Sync, Portable Backup) is opt-in and off by default, so most people never turn one on. This prompt closes that gap. Setup Backup to Gmail is the one exception on the wording: it emails configuration only and never the database, so it is offered as a quick convenience but does not itself cover the data-loss risk this page is about.
It is consent-first: it never turns a backup on by itself. Uploading a copy of someone's whole database off their machine without asking is a privacy violation, so the prompt only asks, then acts on the user's choice.
Where to find it
Where you see it
- A slim banner across the top of the app (accent-toned, not alarming): "Your projects and history live only on this computer. If it is lost, stolen, or its disk fails, there is no copy anywhere else. Set up an off-machine backup so you never lose your work." with a Set up backup button and a Not now (X) dismiss.
- Clicking Set up backup opens a small chooser with two options:
- Back up to Gmail — Omniscio emails an encrypted copy to your Google account on a schedule (quick to turn on). If no Google account is connected yet, the option is honest about it: "You will connect your Google account first…".
- Back up to a cloud folder — save an encrypted copy to Dropbox, OneDrive, or iCloud Drive; it captures everything and you set a passphrase.
- Each choice opens the matching Settings → Backup & Restore section (Setup Backup or Backup Mirror), which is where the real configuration — folder pick, passphrase, and the "I've saved my passphrase" safety step — already lives. The prompt routes you there; it does not re-implement config, and it flips nothing on by itself.
- Settings → Backup & Restore → Automatic Backups carries a standing warning whenever no off-machine backup is on: "No off-machine backup", explaining that a lost, stolen, or failed drive would take the data and every backup of it together. Its copy names the Backup Mirror, so it carries a Set up Backup Mirror button that scrolls straight to that card and highlights it. Like everything else here it only takes you there — it never turns the mirror on, because copying a database somewhere new is the user's decision.
- A mechanism counts as an off-machine copy only when it can actually write a copy of the
database:
hasOffMachineBackup(src/shared/backup-mirror-activation.ts) requires the Backup Mirror to have its folder and passphrase, counts Cross-Device Sync only while this machine is signed in and enrolled — the switch alone writes nothing, because a signed-out or never-enrolled device syncs nothing — and does not count the Portable Backup lab toggle (a manual export that puts nothing anywhere until you run it). Setup Backup to Gmail does not count either (L26-F02): its bundle carries the configuration rows and never the database file, so a Gmail-only user still has no copy of their data that survives the machine and the warning correctly stays up. So an enabled-but-unfinished mirror keeps the warning up instead of looking like protection. The same gate decides whether thebackup-colocatedinbox card clears. - The Tasks view carries its own standing notice. While no off-machine copy exists, the top of
the Tasks screen shows a slim bar reading "Your tasks exist only on this computer. If it is lost,
stolen, or its drive fails, every task, checklist, and attachment is gone." with a Set up an
off-machine backup button and a dismiss (X) control. The X acknowledges the risk and persists
tasksV2OffMachineBackupNoticeDismissed, so the notice stays gone; otherwise it remains until the Backup Mirror is fully configured and then disappears on its own. Cross-Device Sync never clears this notice: the sync allow-list (SYNC_TABLES,src/main/services/sync/sync-oplog-capture.ts) carries no Tasks table, so an enrolled device replicates sessions, conversations, settings and automations but not the tasks, checklists or attachment records. A task's attachment FILE can still be uploaded to the locker as an orphaned blob — no synced row reattaches it on another device, so the task it belonged to does not come back. That flag is deliberately separate frombackupOffMachineSetupOfferDismissed, which the dormant first-run offer also writes the moment someone merely PICKS a backup route — reading that one here would silence the warning for an install whose backup was started and never finished. The button opens Settings → Backup & Restore → Backup Mirror, where the folder and the passphrase are set; like everything else here it only takes you there and turns nothing on. The notice waits for the full settings to load before it judges anything, so a phone or a minimal client that only has a partial copy of the settings never shows a false alarm. - This post-onboarding banner is no longer the only surface for the off-machine backup message: the matching Setup v2 onboarding frame ("Keep a backup off this computer") was REMOVED, so the message is deferred to the surfaces above right after setup rather than shown mid-onboarding.
How it behaves
When it shows
Only on a desktop install where the user is past onboarding, has no off-machine copy of
their data yet (Backup Mirror off, mirror auto-sync off), and
has not already dismissed the prompt. It never shows on the mobile web embed, never
mid-onboarding, and never once you already have a whole-data off-machine backup. Setup Backup
to Gmail does not count: its bundle carries 18 configuration tables and none of the Tasks
tables, sessions, notes or boards, so a Gmail-only user still gets the prompt — worded to say
their settings are backed up but their work is not. It is shown at
most once — dismissing it (or choosing a mechanism) sets backupOffMachineSetupOfferDismissed
so it never returns. You can always set a backup up later from Settings → Backup & Restore.
Also fixed: the database-error dialog
The fatal "could not open its database" dialog used to steer a recoverer only to the
same-volume backups folder — the exact copy a disk loss destroys. It now keeps that
hint for a damaged-but-present database, but adds honest guidance for a disk/machine
loss: "…that local 'backups' folder is unreliable too… Restore from an off-machine
backup instead: the encrypted copy sent to your Gmail, or your cloud backup folder."
Related
- backup-mirror.md — the encrypted folder-mirror backup this prompt routes you into.
- data-folder-recovery.md — what to do when the data folder itself has gone missing.
- inbox-alerts.md — the persistent card the same risk raises now that the banner is off.
Last verified 2026-11-05