Grok Bot Vault is the settings screen where I'd put every login, card and address a Bot needs, so it can sign in and check out while the secret values stay hidden from it.
This walkthrough is the exact order I'd follow on a fresh account: eight steps, the settings to touch, and the gotchas the Vault and secure sign-in docs flag.
Want my team to look over your agent setup with you? Book a free SEO strategy session and bring your list of logins.
Three secure stores, three different jobs
Grok Bot has more than one place for sensitive values, and mixing them up is the first mistake people make.
- Vault: logins, cards and contact info, under Settings then Vault.
- Secure secret card: API keys and any other secret that is not a login or card. It appears in the chat when a Bot asks.
- Team Bot Secrets: environment-variable style keys on a shared Bot, added from the Bot's details.
Each of these keeps the value away from the Bot.
Vault is the one you set up by hand, so that's where we start.
| Value | Store | Bot can read it? |
|---|---|---|
| Website password | Vault login | No, it only knows the login exists |
| Card number and security code | Vault card | No |
| Name, address, phone, email | Vault contact info | Yes, so it can type them into forms |
| API key | Secure secret card | No, the field is masked |
| Shared team key | Team Bot Secrets | Only the description |
Before step 1: check the version and the iPhone bug
Vault needs Grok Bot 0.75.2 or later.
Update the desktop app first and confirm Vault appears in Settings.
If you set things up from an iPhone, check the app version too.
On iPhone 1.18.0 running iOS 26 or later, the Login screen under New item shows only a back button, so a login typed there never saves.
xAI fixed that in iPhone 1.19.0.
Cards and contact info were never affected, but I'd do the whole first pass on desktop anyway, because CSV import is desktop only.
Step 1: Save your most-used login
Open Settings, then Vault, and choose New item.
Pick Login.
Fill in the Website, the Username or email, and the Password, then choose Save login.
Start with the one site your Bot will touch most, such as your CMS or a supplier portal.
From now on the Bot reaches for this entry before anything else when that site asks it to sign in.
It knows the entry is there, which is how it picks the right one, but the password itself is filled into the page without passing through the Bot.
Step 2: Decide whether a card belongs in Vault at all
This is the setting I'd think hardest about.
Per the docs, once a card sits in Vault it is used at checkout with no prompt, and no toggle forces a per-use approval.
So the question is simple: do you want the Bot paying on its own?
If yes, choose New item, then Card, and use Scan with camera or Upload a photo to fill it, or type it in, then choose Save card.
If no, skip this step and enter the card in a Secure Form at checkout with the save box unticked.
That keeps the card for that one chat only.
My Grok Bot shopping setup guide covers the order cards and wallets that sit on top of this choice.
🔥 Want the Vault checklist and Ask first rules I'd use? Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members building agent setups like this one. → Join the AI Profit Boardroom
Step 3: Add contact info, then write a hint for every entry
Choose New item, then Contact info.
Enter the name, address, phone and email you use for shipping and billing, and choose Save contact info.
Unlike passwords, the Bot can read these details, because it types them into forms for you.
Now go back to each entry and fill in Hints.
A hint is a plain sentence telling Bots when to use that entry, for example "Use for work purchases".
When two entries could fit, the Bot follows the hint.
Hints are the closest thing Vault has to routing, so write them for every login and card, not just the ones that look alike.
Step 4: Bulk import the rest from a CSV
Typing logins one by one gets old fast.
On desktop, open New item and pick Import from CSV, then point Choose CSV file at your export.
Supported sources: Bitwarden, LastPass, Firefox, 1Password, Safari or Apple Passwords, and Chrome or Edge.
The import rules worth knowing:
- The file stays on your computer and is never uploaded.
- It has to be under 5 MB.
- Anything already in your Vault is skipped.
- Rows missing a password, or pointing at a site that isn't https, are dropped.
- LastPass files carry cards along with the logins.
Review the list before you press the import button, which shows how many items are ready.
Then delete the CSV, because it holds every password in plain text.
Step 5: Connect 1Password as the fallback
When a login isn't in Vault, the Bot tries a connected password manager next, and only then asks you with a Secure Form.
The computer and apps docs describe the 1Password connection: choose Connect apps, open 1Password under Password Managers, and choose Connect 1Password on your computer.
You approve each login inside 1Password, and it fills the login into the Bot's browser.
The docs list 1Password 8.12.42 or later, personal and Family accounts, and logins from your Personal vault only, called Private on Family accounts.
1Password does not fill payment cards, so cards still come from Vault or a Secure Form.
Step 6: Route every API key through the secure secret card
Never paste a key into chat, a Shell command or a file on the computer.
When a Bot needs a key, it shows the secure secret card.
The field is masked; choose Save securely, and the card confirms with Saved.
The value doesn't land in the transcript and isn't shown to the Bot.
There's a practical reason beyond privacy too.
Recover, Reset and computer updates remove installed apps and packages, so a key you typed into a shell profile or tool config can vanish with them.
Keys in the secure card, in Vault or under Team Bot Secrets survive those resets.
📞 Mapping logins and keys across several Bots? Book a free SEO strategy session and my team will help you plan which Bot gets which access. → Grab your free session
Step 7: Add Ask first rules for checkout and sign-ups
Vault decides what a Bot can use.
Auto Review decides when it has to stop and ask you.
Per the approvals, security and privacy page, the Auto-review switch lives in Settings, General, under Bot, and Custom Rules appear under it on desktop.
Add a rule by describing one action, choosing Ask first, and pressing Add Rule.
The two I'd add on day one:
- Ask first before completing any checkout or payment.
- Ask first before creating an account on a new website.
An Ask first rule always stops a matching action, and it beats an Allow rule when both match.
You get up to 20 of each kind, and each can run to 1,000 characters, but narrow rules work better than broad ones.
Step 8: Give Team Bots their own logins and Secrets
Your personal Vault doesn't reach Team Bots.
A Team Bot can't use your logins, cards or contact info at all.
If you own or manage one, the path is wrench, Manage, General, Bot's accounts.
From there pick Add and Bot's vault login, fill in the Website, Username or email and Password, and choose Save login.
Only managers can see or change these, and they never appear in your own Vault.
For keys, go to Secrets on the Team Bot and use Add secret: it takes an environment variable name, a short description and the value.
The Bot reads the description and never the value, but every teammate's chat uses that secret, so only add keys you'd share with the whole team.
Gotchas to check once everything is saved
- No per-Bot scoping: every item in your Vault is open to every Bot on the account. Hints steer the choice; they don't lock anything.
- Write-only values: passwords stay hidden and cards show the last four digits. To change a secret you choose Replace; the old value can't be read back.
- Card numbers: to change one, delete the card and save it fresh. Phone editing of saved cards isn't available yet.
- What the Bot may edit: contact info, nicknames and hints, on request. Anything secret, from passwords and usernames to websites, card numbers and security codes, is edited only in Settings, Vault.
- Chat details get saved: a name, address, phone or email you give in chat is saved as contact info once the task finishes, and the Bot tells you. Say so if you don't want it kept.
- Forms without the checkbox: a Secure Form with no "Securely save to Bot's vault" option saves straight to Vault.
When a sign-in step needs your hands
Some steps can't go through a form.
The docs list single sign-on, passkeys, a CAPTCHA the Bot couldn't clear, approval on another device, QR codes and bank card verification.
Choose Take over on the request, or open the computer and choose Take control.
Do only that step, press I'm done, then send the Bot back to work.
The signed-in session stays on the computer for later tasks and is shared by all your Bots, so you usually do this once per site.
One-time codes are easier: the Bot picks them up from a linked Gmail or Outlook mailbox, or its own inbox.
If a saved secret seems to have disappeared
A blank field is not proof that a secret was deleted.
Shell not printing a value doesn't mean it's gone either.
On a Team Bot, if the secret's name is still listed under Secrets, the value is still stored.
If the name is missing and you never chose Remove, fully quit Grok Bot and reopen it, then check on a second device, and press Try Again if the list shows an error.
Only add it again once it's missing everywhere, and don't keep a backup copy in a file on the computer.
Inside the AI Profit Boardroom I share the rest of my agent setup routines alongside this one.
Also On Our Network
- 🌐 What shops, service firms and agencies should save in Vault, and what not to
- 🌐 An eight-row scorecard of Vault, from secret handling to saved-card payments
- 🌐 Five copy-paste prompts that make Vault the key cabinet of your Agent OS
- 🌐 Which GoldieBench models to pair with Vault for access maps and onboarding pages
FAQ: Grok Bot Vault
Where is Grok Bot Vault?
Open Settings, then Vault, in the desktop app or on your phone. It needs Grok Bot 0.75.2 or later.
Why won't my login save on iPhone?
On iPhone 1.18.0 with iOS 26 or later, the Login screen shows only a back button. Update to iPhone 1.19.0, or add the login on desktop.
Which password managers can I import from?
On desktop, Import from CSV accepts exports from 1Password, Chrome or Edge, Safari or Apple Passwords, Firefox, Bitwarden and LastPass. The file must be under 5 MB.
Does 1Password fill cards for Grok Bot?
No. The docs say 1Password does not fill payment cards, so cards come from Vault or a Secure Form.
How many Ask first rules can I add?
Up to 20 Ask first rules and up to 20 Allow automatically rules, each up to 1,000 characters.
📺 Video notes + links to the tools 👉
🎥 Learn how I make these videos 👉
🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
→ Get my best AI training inside the AI Profit Boardroom
Run these eight steps in order, then book a free SEO strategy session or join the AI Profit Boardroom to keep building on your Grok Bot Vault.











