A password list can look tidy while several accounts still share the same secret. The Security check in the browser Vault helps you find weak passwords, repeated values, and older entries stored in OGAD (Off Grid AI Desktop).
The check runs against the local Pro Vault. It gives you a repair list, not proof that an account is compromised. You still need to change each password on the real website and then update its saved Vault entry.
Download OGAD | Desktop beta 122 release notes
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@getoffgridai.co, join our Slack community, or talk to us on Reddit.
What does Security check measure?
The view shows a score from 0 to 100 and groups findings under Weak passwords, Same password, group N, and Old passwords. Older entries are those whose password has not been changed in about a year.
Each category answers a different question. A weak password may be unsuitable on its own. A reused value connects several accounts to the same secret. An old value is a prompt to review the entry's age, not evidence that somebody stole it.
The audit is computed by the desktop. Passwords are not sent to a language model or exported into the browser panel merely to calculate the score. This check is not a breach-database search and cannot certify that every account is safe.
Open the check for the intended Vault
Install OGAD, unlock its Pro Vault, and connect the browser extension. Confirm which desktop the browser is paired with before you review the results.
Open the Vault's Security check and wait for the summary. If the Vault is locked or the desktop is unavailable, fix that connection first. A missing result does not mean the Vault has no weak passwords.
Choose a small set of accounts to repair in this session. Start with records you can identify and access. Do not make a long list of exposed password values in a separate note; use item names to track your work.
Fix a reused-password group
Open one Same password group and identify the accounts it contains. Visit each account's real password-change page. Use a distinct new value for each account rather than replacing the shared password with another shared password.
A practical sequence for one account is:
- Check the website address and sign in through its normal flow.
- Open its password-change form.
- Generate a new value with the Vault's Password generator.
- Submit the change on the website and wait for confirmation.
- Update the matching saved login in the Vault.
- Test a fresh sign-in before moving to the next account.
Changing the saved entry first does not change the server-side account. If the website rejects the change, retain the credential that still works until you complete the site's process.
Handle weak passwords and old entries
For a weak-password finding, check the website's accepted length and character rules, then use the generator to make a new value that fits. Avoid reusing a value from another item simply because that item received no warning.
For an old entry, first decide whether the account is still used. Check whether the record points to the right website and username. A stale duplicate may describe an account you already updated under another name.
The age finding does not require you to assume a breach. Treat it as a review queue. If you decide to replace a password, follow the site's change process and check a new sign-in before you remove the old saved value.
Check the result after each change
Return to Security check after you save the updated item. Review the relevant group rather than looking only at the overall score. A reused group may shrink when one account gets a unique password, even while other accounts in that group still need work.
Keep the repair result tied to a real account action. “Saved item updated” and “website password changed and tested” are different states. The second one is what you need before considering that account repaired.
If a finding remains, inspect whether another duplicate record still contains the old value. Do not delete items merely to improve the score. First establish which records are active and which are obsolete.
Common problems and their next checks
| Problem | Next check |
|---|---|
| Score did not change | Confirm the updated item was saved and rerun the view |
| Reuse warning remains | Inspect every member of the group, including duplicates |
| New saved password fails | Check whether the website accepted the change |
| Old-password finding seems wrong | Check the saved entry and its update history |
A perfect score does not prove that a website, recovery email, browser, or computer is secure. It describes the properties this local check can inspect in the saved records. Keep the score useful by treating it as a guide to specific changes.
Finish one repair before starting ten more
Open OGAD, run the local Vault check, and choose one reused-password group. Change one account on its real website, save the accepted value, and test sign-in. Repeat that complete sequence for the other accounts instead of making unverified edits across the whole Vault.
Top comments (0)