Recover Credentials After an Upgrade

If a previously saved API credential appears missing after upgrading an official build, it may still exist in the older Keychain service. RepoPrompt provides an explicit repair flow; it does not scan legacy accounts automatically at startup.

This flow repairs known secure-storage accounts. It does not sign a CLI runtime into its provider, renew a subscription, or grant API access. First identify the connection in Providers & Models, especially when the same company offers separate CLI and API products.

The legacy service targeted by this repair belongs to earlier RepoPrompt CE builds; it is not a general Classic import. For that transition, see Migrating from Classic to RepoPrompt CE.

Inspect known legacy accounts

1. Open Settings → Models & Providers → API Providers.
2. Under Legacy secure storage repair, choose Review….
3. Choose Scan Known Accounts. Scanning is noninteractive; importing a selected account may subsequently request macOS Keychain approval.
4. Read the status for the intended account before choosing an action.

No legacy value means that scan did not find a value for that known account; it does not prove that the credential never existed elsewhere. Ready to import and Import may require Keychain approval identify accounts you can attempt to import.

Import without replacing a current value

Choose Import for the relevant account and respond to any Keychain prompt. A successful import reports Imported and verified. Legacy values are retained by default so that an older build can still use them.

If the status says A different v2 value already exists, automatic replacement is withheld. Replace v2… opens a separate confirmation. Replace only when you intend to overwrite that account's current stored value; the legacy value is still retained.

“Verified” describes the storage repair result. Check the relevant provider's connection or validation control separately to confirm that the credential still works with the service.

Cancelled or failed imports

Import was cancelled and Repair failed; retry this account allow another import attempt. Read the reported state, check whether a Keychain request needs attention, and retry the affected account. Rescan refreshes the known-account list. If no usable legacy value is available, re-enter the credential using the appropriate provider guide.

Keep rollback possible

After a verified import, Delete Legacy… may be available. Its confirmation explains that deleting the old value can make a return to an older build require re-entry. Deletion is optional and separate from importing; leave the legacy value in place when you still need rollback access.

For a locally built app, check How to Build as well: ad-hoc debug builds use temporary secure storage, so losing saved credentials after quitting can be expected for that build type rather than an upgrade migration failure.