You can keep a supported authenticator setup key with a login in the local Vault in OGAD (Off Grid AI Desktop). The paired browser extension can show the current one-time code and its countdown, so you can complete a sign-in from your computer.
This guide uses the One-time code secret field in a login item. It covers the released Pro Vault workflow, not a separate phone authenticator, automatic QR import, or every kind of two-factor sign-in.
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 type of code does this support?
The login field accepts a supported authenticator setup key or an otpauth:// link. The Vault uses that secret to calculate changing, time-based codes. The code visible today is not the setup key you must store.
A text-message code, an email code, a hardware security-key request, and an approval notification are different sign-in methods. Putting their text in this field does not turn them into a time-based authenticator.
The setup key can recreate the codes. Treat it as a secret. Do not paste it into an AI chat to ask the model to configure it, and do not put a real key in a screenshot used for support.
Prepare the account and the Vault
Set up OGAD, unlock its Pro Vault, and connect the browser extension. Open the account's real security-settings page and check its domain before changing its sign-in method.
Keep a working sign-in method until you finish the setup. If the service gives you recovery codes, store them using a recovery plan you can use when the computer or Vault is unavailable. A code generator cannot recover a locked Vault by itself.
This workflow puts the password and authenticator secret in the same local Vault when you store both in one login. Decide whether that arrangement fits your account requirements. It is not the same separation as keeping the second factor on another physical device.
Add the setup key to the correct login
- On the website, choose its authenticator-app setup process.
- Find the text setup key or supported
otpauth://value offered by the service. - Open the matching login item in the browser Vault.
- Edit One-time code secret and enter that setup value.
- Check Websites and Username, then choose Save.
- Open the saved item and use its current Authenticator code to finish the website's setup check.
Do not store the six-digit code from that moment as the secret. It will expire. The setup value is the input the generator needs for future codes.
If the website only presents a QR image, use its own option to display the text key if available. This guide does not assume that the released extension can scan every QR image from a page.
Use the code for a later sign-in
Open the real login page and fill or enter the saved username and password. When the website asks for the authenticator code, open the saved login's Authenticator code and copy the current value.
Watch the countdown. If the code is close to its change, wait for the next value before entering it. Submit it promptly. Some supported forms can accept a code through Vault filling, but manually copying the value remains useful when a site uses an unusual set of input boxes.
Check the account name before you copy. Two similar entries can produce valid codes for different accounts at the same service. A code with the right length is not proof that it belongs to the account you are signing into.
Why is the website rejecting a code?
| Symptom | Check | Action |
|---|---|---|
| Code expires during entry | Countdown | Wait for a fresh value and submit promptly |
| Every code fails | Computer date and time | Correct the clock, then try a new code |
| Correct password, wrong code | Account and setup key | Check the saved login against that account |
| No code appears | Secret field and Vault lock state | Check the saved setup value and unlock the Vault |
Repeated failure is not a reason to disable the account's sign-in protection. Use the service's supported recovery process if you cannot complete the setup. Avoid replacing the secret at random while another authenticator still works.
What works without internet?
Once the supported setup secret is stored, calculating a time-based code does not need a cloud AI service or a chat model. The local desktop Vault still needs to be accessible to the browser extension.
The website you are signing into usually needs internet. Therefore, local code generation does not make the complete website sign-in an offline task. The computer's clock also needs to be correct; a code can be calculated locally and still fail because the time is wrong.
Locking the desktop Vault removes browser access to the open entries. If the computer is unavailable, follow the recovery route you prepared with the account provider. Do not assume this desktop workflow has copied authenticator secrets to your phone.
Start with one account you can recover
Choose an account with a recovery method you have checked. Set up its login in OGAD, save the supported setup key, complete the website's verification, and test a later sign-in before you change other accounts.
Top comments (0)