Fix sign-ins after a restore
After you restore a backup on another computer, a checklist shows which keys and sign-ins need entering again, and what else to set up.
Your saved keys and sign-ins are locked to the computer that saved them. After you restore a backup from another computer, Yardmaster cannot read them, so the Post-Restore Credential Check lists each one that needs entering again, with a button that takes you to it.
Work through the checklist#
The checklist opens by itself the first time Yardmaster starts after a restore that replaced your data with a backup from another computer, and an Inbox card points to it.
Look at the groups that are open: those have items that need attention. Each group shows how many items are healthy.
On an item, click its button: for example Go to Accounts to sign in again, or Copy or Open Terminal for a command-line tool's sign-in command.
Enter the key or sign in again.
Come back and click Re-check on that item. It turns healthy when Yardmaster can read it.
When you are done, or want to finish later, click Dismiss.
If items still need attention when you click Dismiss, Yardmaster asks first. The checklist does not open by itself again until your next restore.
If you undo the restore, the checklist does not open for it: your own keys and sign-ins come back with your own settings.
Run the check any time#
Open Settings > Backup & Restore.
Under Post-restore credential check, click Run credential check….
Refresh All in the checklist checks everything again from the start.
Restored an older backup?#
Your data goes back to the day the backup was made, so any key or account you added after that is not in it, even on the same computer. A second Inbox card names the backup's date and links to Settings > Accounts.
What a backup does not bring with it#
Some things live outside Yardmaster and stay on the old computer. After a move, check:
Command-line tools, such as GitHub CLI: open Settings > Connected Tools to install what is missing, then sign in to each one (the checklist lists GitHub CLI, Google Cloud SDK, Google Workspace CLI and gogcli).
Claude Code's own files: its
settings.json, skills and scripts in the.claudefolder in your home folder. Copy them from the old computer. (YourCLAUDE.mdand memory files do come with a Backup Mirror or a Portable Backup.)Your project folders. Copy or clone them to the new computer. If a folder is in a different place, edit the project to point at it.
SSH keys for remote computers: copy them over, or make new ones in Settings > SSH Remotes.
Cron Jobs: their secret values and any folder paths. Edit each job, enter the values again, and run it once by hand to check.
Yardmaster writes the .claude/amc-instructions.md and .claude/settings.json files in a project again before each session, so those need nothing from you.
What it checks, in 13 groups: Yardmaster accounts, provider API keys, MCP server secrets, integration tokens, Google sign-in, automation credentials, Cron Job secrets, backup passphrases, command-line tool sign-ins, SSH remotes, environment, installed tools, and cloud infrastructure.
Some Environment and Cloud Infrastructure items are for people who build Yardmaster itself (a worktree drive, a secrets vault, a repo pointer, a cloud test key). If you never set those up, they show as missing; you can ignore them.
Restoring on the same computer skips the checklist, because the saved copies are still readable there.
Checks only look at this computer. A healthy row means Yardmaster can read the saved key, not that the provider accepted it.
Commands that need your email address can only be copied: replace
<email>before you run them. Opening a terminal does not mark the item fixed; click Re-check after you sign in.
Related
- See and remove your stored keysStored Keys lists every API key and secret Yardmaster keeps on this computer, by name only, so you can find, replace or delete them without ever showing a value.
- Back up everything to a folderBackup Mirror keeps an encrypted copy of all your Yardmaster data in a folder you choose, such as a Dropbox or OneDrive folder, so a broken or new computer loses nothing.