Post-Restore Credential Wizard
What happens when a restore onto a different machine leaves saved credentials undecryptable: the wizard that opens after the restore, the fourteen credential categories it probes, the fix actions it offers per broken item, and the inbox alert and CLI route that surface the same health report.
On this page
What it is
After a Backup Mirror replace-mode restore on a different machine, Omniscio auto-detects that some saved credentials can no longer be decrypted and walks you through re-entering them.
When you restore an Omniscio backup onto a new computer, the OS-level encryption key (DPAPI on Windows, Keychain on macOS) changes. Every credential that was encrypted with the old machine's key — API keys, OAuth tokens, MCP server secrets — decrypts to an empty string. The Post-Restore Credential Wizard automatically opens after a restore, shows which credentials are broken, and links you to the right settings screen to fix each one.
Where to find it
The wizard opens by itself: after a restore that brought credentials over from another machine, Omniscio detects it at startup and raises the wizard modal. You can also run the credential health check at any time — not just after a restore:
- Settings → Backup & Restore → "Run credential check…" opens the same wizard
How it behaves
How it works
- Detection: When Omniscio starts after a restore, the startup sequence detects the consumed restore flag. If the restore came from a different machine (hostname mismatch), it sets
postRestoreWizardPending = true. Same-machine restores skip the wizard since DPAPI keys survive. - Auto-open: The
PostRestoreWizardGatecomponent watches that flag and opens the wizard modal automatically. - Health report: The wizard probes fourteen categories (returning both healthy and broken items for each):
- Omniscio Accounts — login and API key accounts that failed to decrypt
- Provider API Keys — AI provider keys (OpenAI, Gemini, Groq, DeepSeek, etc.), including each saved GLM (z.ai) multi-account key (those live in a database table, not
config.json, so they're checked separately) - MCP Server Secrets — encrypted environment variables and headers for MCP servers
- Integration Tokens — third-party service tokens (Slack, Jira, Ollert, Linear, Notion, etc.)
- Google Authentication — OAuth refresh/ID/access tokens for Google integration
- Automation Credentials — encrypted credentials used by automation rules
- Cron Job Secrets — encrypted environment variables in active cron jobs
- Backup Passphrases — setup backup and mirror backup passphrases
- CLI Authentication — checks
gh,gcloud,gws,gogsign-in status, only for the tools the Toolchain check finds installed. A tool that is not installed never shows as "not authenticated". - SSH Remotes — verifies each remote's SSH identity/key file exists on disk, plus the app-managed
known_hostshost-key pins (a warning when they're missing: your remotes still connect, but the first reconnect re-records each host key instead of verifying it, so confirm the server identity that first time) - Environment — checks the worktree drive path and Claude Code config files (~/.claude/). The developer-only rows — the repo path pointer,
~/.claude/scripts, and the secrets vault — appear only on a developer machine (running from source, or a build that sits inside an Omniscio checkout). - Toolchain — reports required tools (Claude Code, Claude sign-in, Git) that are missing or errored. Optional tools appear only when installed, so a missing optional tool is never counted as needing attention.
- Cloud Infrastructure — developer machines only: whether this machine's cloud product key is present. A broken row points at the command that re-mints it. Healthy when present, broken with that remedy when absent, and nothing at all when it cannot tell.
- Database Encryption — if the database is encrypted, warns when the OS-keyring key did not survive the move to this machine, so the recovery code is now the only way to open it (the one credential whose loss is irreversible data loss, unlike the re-enterable categories above)
- Collapsible sections: Each category shows as a collapsible section with an "N of M healthy" counter. Categories with broken items expand by default; all-healthy categories collapse.
- Fix action buttons: Each broken item has context-specific action buttons:
- Go to Accounts/Settings — navigates to the relevant settings section
- Copy — copies a CLI command to the clipboard
- Open Terminal — copies the command AND launches a visible terminal window
- A remedy you must edit before it will run gets Copy only, no Open Terminal —
gog auth add <email>needs your own address substituted, so there is nothing to launch. A button that cannot work is not offered. - If a launch is refused or fails, the wizard now says so instead of doing nothing.
- Per-item re-check: After you re-enter a credential, click Re-check next to that item. The wizard re-probes just that credential and updates it in-place.
- Dismiss: When all credentials are fixed (or you choose to fix them later), dismiss the wizard. A confirmation dialog warns you if broken items remain. The wizard won't reappear until the next restore.
Inbox integration
When broken credentials are detected after a restore, an inbox alert is raised:
"X credentials need re-entry after restore"
The alert links to the credential wizard in Settings → Backup & Restore. It deduplicates (only one active alert at a time) and follows standard inbox affordances (snooze, archive, dismiss).
Secrets Omniscio issues itself
Not everything that becomes unreadable is something you re-enter. Two of the encrypted values are machine-issued: the CLI control token and the VAPID push private key. Your computer was not the only holder of those — every script and agent holding the CLI token has the first, and every subscribed phone has the second. (The Real Chrome Bridge pairing token was a third until My Real Chrome — Full was deleted on 2026-10-17.)
Those two are kept, never replaced. If the keyring cannot unlock one, Omniscio leaves the stored value exactly as it is and the feature that depends on it waits:
| Unreadable secret | What you notice | What fixes it |
|---|---|---|
| CLI control token | Agents and external scripts fail to authenticate | Fix the machine-level keyring, then restart Omniscio — and the ~/.amc/cli-token file is never overwritten with a blank. |
| VAPID push private key | Push notifications stop arriving | Same — and no device has to re-subscribe. |
The alternative (generate a fresh secret) would quietly erase the original and force you to hand every script a new token or re-subscribe every phone to recover from a fault that was temporary. If you would rather rotate than wait, Settings → CLI Control's Regenerate button still does that deliberately.
A save never erases a key the app could not read
The same rule now covers every stored secret, not just those three: your API keys, sign-in tokens and the Google sign-in secret. While Omniscio cannot read a stored secret (the keyring is locked, or the background half of the app has not reached it yet), saving settings keeps that secret sealed on disk instead of writing it empty. Once the keyring reads again, the key is simply back. One side effect: clearing a key Omniscio cannot read right now does not stick. Clear it again once the keyring works. Clearing a key it can read works as always, and a clear saved by one part of the app reaches the rest of it.
If the CLI token file ever ends up holding an older key than the one Omniscio is using, the app rewrites the file within a minute. A newer key in the file is left alone.
When this happens an inbox alert names the affected feature, so an outage is never silent — these two fields are deliberately outside the fourteen wizard categories above, since there is nothing for you to re-enter and the wizard's "fix it" actions do not apply.
Related
Backup Mirror is the backup and restore system that creates the condition this wizard addresses. Machine Migration is the full migration guide, including the re-authentication checklist a move to a new computer implies. And Is my data encrypted? explains what Omniscio encrypts at rest, which is why the credentials above cannot be decrypted on a new machine.
Last verified 2026-10-06