Grok Bot can now remember your website logins, payment cards and addresses in a Vault, so your Bot can sign in and check out without asking you every time. You set it up under Settings > Vault on desktop or phone, and you need Grok Bot 0.75.2 or later. The one thing to know before you save a card: according to the official help page, there is no setting that makes your Bot ask before it uses a saved card. If you want to approve every purchase yourself, don’t save cards to the Vault. This guide shows how to set it up, what the Bot actually sees, and the safe way to handle payments.

Key facts (from the official Grok Bot help page on secrets and the Grok Bot changelog):

• Shipped: v0.75.5, October 23, 2026. Requires Grok Bot 0.75.2 or later.
• Where: Settings > Vault, on desktop and on the phone.
• What it stores: logins (website, username or email, password), cards (number, expiry, security code, name, billing address) and contact info (names, addresses, phones, emails).
• What the Bot sees: never your saved passwords, card numbers or security codes. It can see your contact info and which logins you saved.
• Scope: account-wide. Every Bot on your account can use every Vault item, and you can’t limit an item to one Bot.
• Not supported: Team Bots. They use Secrets instead.
• Payment approval: no setting requires your approval each time a saved card is used.

What the Vault is for

Grok Bot is an AI assistant that works on its own cloud computer with a browser. It can book things, download bills, fill forms and buy things for you. Until now, a login page or a checkout form meant an interruption. The Bot would ask you for the password or card with a Secure Form, a pop-up form that fills the website without showing the Bot the value. You had to fill that form every single time.

The Vault removes the repetition. You save a login or card once and the Bot fills it into the website the next time it needs it. As with the Secure Form, the password or card number goes into the page without being shown to the Bot.

If you’ve read our guide to letting Claude sign in with 1Password, the idea is the same: the agent uses your credentials without reading them. The big difference is that Grok Bot’s Vault is built in, works on the phone too, and also handles cards and shipping addresses. 1Password for Claude doesn’t support cards.

Before you start

You need three things:

1. Grok Bot 0.75.2 or later. The changelog says Vault “Requires Grok Bot 0.75.2 or later.” If you don’t see Vault in Settings, update the app first.
2. A personal Bot, not a Team Bot. The help page says “Vault isn’t supported on Team Bots.”
3. A decision about cards. Read the payment section below before you save any card.

The changelog doesn’t say Vault is limited to particular plans, and we couldn’t find any plan restriction in the official docs.

Step 1: Open the Vault

Open Grok Bot, go to Settings, and choose Vault. It’s there on the desktop app and on the phone app. You’ll see your saved items and a New item button.

Step 2: Add a login

1. Choose New item, then Login.
2. Enter the Website, your Username or email, and your Password.
3. Choose Save login.

From now on, when your Bot needs to sign in to that website, it uses this login first. The order it follows, per the help page, is:

1. a login saved in the Vault,
2. then a connected password manager such as 1Password,
3. and if neither has it, it asks you with a Secure Form.

Step 3: Add a card (optional, read the warning first)

1. Choose New item, then Card.
2. Choose Scan with camera or Upload a photo to fill the details from the card, or type them in.
3. Choose Save card.

Afterwards the Vault shows only the card’s last four digits. You can also save a card from a chat. When you attach a photo of a card, Grok Bot offers Save to Vault so the Bot can pay with it later.

Step 4: Add contact info for shipping and billing

1. Choose New item, then Contact info.
2. Enter the name, address, phone and email.
3. Choose Save contact info.

Your Bot fills these into shipping and billing fields at checkout. Unlike passwords and card numbers, contact info is visible to the Bot, so it can type it in for you.

Step 5: Add hints so the Bot picks the right entry

Each item has a Hints field. Use it to tell your Bot when to use that entry, for example “Use for work purchases”. The help page says your Bot follows the hint when it chooses between entries.

Hints are worth adding as soon as you have more than one of anything:

• Two cards: “Personal card, use for groceries and subscriptions” and “Company card, use only for work travel”.
• Two logins for the same site: “Work account” and “Personal account”.
• Two addresses: “Home, default shipping” and “Office, only when I say so”.

Step 6 (desktop only): Import logins from your password manager

If you already keep passwords in another manager, you don’t have to type them in one by one. On desktop:

1. Export your passwords as a CSV file from your current manager. The help page lists 1Password, Chrome or Edge, Safari or Apple Passwords, Firefox, Bitwarden and LastPass.
2. In Settings > Vault, choose New item, then Import from CSV….
3. Choose Choose CSV file and pick the export. The file must be under 5 MB. The help page says it is read on your computer and never uploaded.
4. Review the list. Items already in your Vault are skipped. Rows with errors, such as a missing password or a website that isn’t https, aren’t imported.
5. Choose the import button, which shows how many items are ready.

Two things to watch:

• LastPass exports bring cards along too. If you don’t want cards in the Vault (see below), remove them after the import.
• Delete the CSV file afterwards. It holds all your passwords unencrypted. The help page says so explicitly. Delete it and empty your trash.

Think about whether you really want every password in there. Every Bot on your account can use every Vault item, so importing hundreds of logins gives all your Bots access to all those sites. Many people will be better off saving only the handful of logins they actually want a Bot to use.

The other way to save: from a chat

You don’t have to set everything up in advance. When your Bot hits a login page, a card form or an address form, it shows a Secure Form. That form now has a checkbox: Securely save to Bot’s vault.

• Checked: the value is saved to the Vault for next time.
• Unchecked: the value is used only for that chat and expires on its own.

Also note: when you tell your Bot a name, address, phone number or email in chat, the help page says it saves that as contact info once the task is done and tells you what it saved. If you don’t want something kept, say so.

Signing up for new sites

If you let your Bot pick the password when it creates an account for you, the help page says the Vault generates the password and saves the login, and your Bot never sees it. That’s handy, but it means you won’t know that password either unless you look in your own records. The Vault doesn’t show saved passwords: “In Settings > Vault, saved passwords stay hidden.” If you might need to sign in yourself later, set the password yourself or plan to use the site’s password reset.

Payments: the one setting that doesn’t exist

This is the part most people will get wrong. The official help page asks “Will my Bot ask before it uses a saved card?” and answers:

“Not necessarily. Saving a card in Vault lets your Bots fill it in at checkout, and there’s no setting that requires your approval each time a saved card is used.”

So saving a card is effectively giving all your Bots permission to pay with it. Grok Bot does have a general safety check called Auto-review, and the changelog says that before an action it can’t undo, such as buying, a Bot checks your own messages for approval. But the help page is clear that the Vault itself has no per-payment approval switch, so don’t rely on getting a prompt.

If you want to approve every payment yourself, the official advice is simple: don’t save the card.

• At checkout, when your Bot asks for a card with a Secure Form, leave “Securely save to Bot’s vault” unchecked. The card is used only in that chat.
• Be careful with forms that don’t have that checkbox. The help page warns: “A form without that checkbox saves straight to Vault, so don’t submit it.”
• If you already saved a card, open Settings > Vault, select it and choose Remove. After that, Grok Bot can no longer pay with it.

A sensible middle ground if you do want a saved card: use a card with a low limit, or a virtual card from your bank that you can freeze, and add a hint that restricts what it’s for.

What your Bot can change, and what only you can change

From the help page:

Item	Bot can change it when you ask?	Where you change or remove it
Contact info	Yes	Bot or Settings > Vault
Nickname and hints	Yes	Bot or Settings > Vault
Passwords, usernames, websites	No	Settings > Vault only
Card numbers, security codes	No	Settings > Vault only
Removing logins and cards	No	Settings > Vault only

That means a confused or misled Bot can’t quietly change your saved password or swap a card number. But it also means you have to do card and password maintenance yourself.

Editing and removing items

• Edit: open Settings > Vault and select the item.
• Remove: select the item and choose Remove. After you remove a login, Grok Bot can’t sign in with it any more. After you remove a card, it can’t pay with it.
• New card number: you can’t edit a card’s number. Remove the card and add it again.
• On the phone: the help page says saved cards can’t be edited on the phone yet. Use desktop.

Team Bots and API keys: use Secrets instead

The Vault is only for logins, cards and contact info on personal Bots. For other secrets:

• API keys and similar secrets: when a Bot asks for one, it shows a secure secret card with a masked field. Choose Save securely. The value isn’t written into the chat.
• Team Bots: if you own or manage one, open the Bot’s details, go to Secrets, choose Add secret, and enter a variable name, a short description and the value. The description is visible to the Bot; the value isn’t. Remember that a Team Bot’s secrets are used in every teammate’s chat, so only add keys you’re happy for everyone who chats with that Bot to use.

The help page also says plainly: don’t paste secrets into chat, into the Bot’s terminal, or into ordinary files.

Troubleshooting

I can’t find Vault in Settings. Check your app version. Vault needs Grok Bot 0.75.2 or later. Also check you’re on a personal Bot, since Team Bots don’t support it.

The password field looks empty. Was it deleted? Probably not. Saved values are write-only. The help page says “A blank field later is not proof the secret was deleted.” Passwords stay hidden and cards show only their last four digits.

The Bot said “Could not fill into the page.” According to the help page, the page may have moved. The value was still not shown to the Bot. If the Bot asks again, submit a new card or form.

I saw “The secret was not saved. Try again.” The save failed. Try again.

I updated or reset the Bot’s computer. Are my Vault items gone? No. The help page says Recover, Reset and computer updates remove installed apps and packages, and that is separate from secrets saved with the secure card, under Secrets, or in the Vault.

The Bot used the wrong card or login. Add or sharpen the Hints on each entry, or tell the Bot in your request which one to use. If a card should never be used without you, remove it from the Vault.

My CSV import skipped some rows. Rows with a missing password or a non-https website aren’t imported, and items already in the Vault are skipped. Fix the rows in your password manager and export again, or add those logins by hand.

FAQ

Does the Bot ever see my password? The help page says your Bot never sees a saved password, card number or security code. It can see your contact info and the list of logins you’ve saved, so it can pick the right one.

Can I keep a login just for one of my Bots? No. “Vault covers your whole account. Everything you save is available to every Bot on your account, and you can’t limit an item to one Bot.”

Does it work with 1Password? Yes, alongside it. When signing in, the Bot tries the Vault first, then a connected password manager such as 1Password, and only then asks you.

Will my Bot buy things without asking if I save a card? It can. There’s no Vault setting that forces approval for each use of a saved card. If that worries you, don’t save cards and use the one-time Secure Form at checkout instead.

Can I use it on my phone? Yes. Vault is in Settings on the phone too. CSV import is desktop only, and saved cards can’t be edited on the phone yet.

Does it cost extra? The changelog doesn’t mention any price or plan limit for Vault.

The short version

1. Update to Grok Bot 0.75.2 or later and open Settings > Vault.
2. Save the logins you actually want your Bots to use, and add hints.
3. Import from your password manager only if you’re comfortable giving every Bot access to all of them, then delete the CSV.
4. Save contact info for shipping and billing.
5. Think twice about cards. Saved cards can be used without a per-payment prompt. To approve each purchase, leave “Securely save to Bot’s vault” unchecked at checkout.

For more on Grok’s agent tools, see our Grok Build guide and our coverage of Grok Bot for Enterprise. More hands-on guides are on the 7minai homepage.

Sources: Grok Bot help: Store secrets securely; Grok Bot changelog, v0.75.5 (October 23, 2026).