Guide from the official docs

How to use Grok Bot's Vault for logins and cards

Where Grok Bot's Vault is, what it stores, how to add, edit and remove logins, cards and contact info, and how Bots use them at sign-in and checkout.

By AideDex desk · published · updated

This guide follows the official docs and announcements, linked inline. AideDex did not test these products and does not score them. How we check facts.

Last checked Oct 25, 2026; Vault scope, hand-off steps and the Team Bot Vault re-checked Nov 3, 2026.

Vault is the place in Grok Bot’s Settings where you save logins, cards and contact info so a Bot can sign in to sites and check out for you (Cursor Help). That help page, “Store secrets securely”, is the one xAI’s own Grok Bot docs link to for secrets (xAI Docs). Open Settings > Vault, choose New item, pick Login, Card or Contact info, fill it in and save. Per the help page, the Bot never sees a saved password, card number or security code, and it doesn’t ask each time it uses a saved card. Vault is listed in the Grok Bot 0.75.5 changelog entry, dated Oct 23, 2026 (which also covers 0.75.3 and 0.75.4), and needs Grok Bot 0.75.2 or later (xAI changelog).

What Vault stores

The help page lists three item types (Cursor Help):

ItemWhat you enterWhat the Bot can see
LoginWebsite, username or email, passwordWhich logins you saved; not the password
CardNumber, expiry, security code, name on card, billing addressNot the card number or security code
Contact infoNames, addresses, phone numbers, emailsThe contact details themselves

The Bot can see contact info and the list of saved logins “so it can pick the right entry and type contact details in for you” (Cursor Help).

Vault is not for API keys. For those, the docs point to the secure secret card a Bot shows when it needs one (Cursor Help). xAI’s docs say the value you enter there is masked, kept out of the transcript and not shown to the model (xAI Docs).

Where to find it

Vault is at Settings > Vault “on desktop and on the phone” (Cursor Help). Grok Bot runs on macOS, Windows and Linux desktops, on iPhone with iOS 18 or later, iPad with iPadOS 18 or later, and Android 9 or later (xAI Docs FAQ). Settings opens with Cmd/Ctrl+, on desktop (xAI Docs FAQ).

If you don’t see Vault, check your app version. The changelog says the feature requires Grok Bot 0.75.2 or later (xAI changelog). Vault isn’t supported on shared Bots; for a shared Bot you add keys under Secrets instead (Cursor Help).

How to add a login, card or contact info

From Settings, per the help page (Cursor Help):

  1. Open Settings > Vault and choose New item.
  2. Pick Login, Card or Contact info.
  3. Fill in the details and save:
    • Login: enter Website, Username or email and Password, then choose Save login.
    • Card: choose Scan with camera or Upload a photo to fill it from the card, or type it in, then choose Save card.
    • Contact info: enter name, address, phone and email, then choose Save contact info.

Each item has a Hints field. You write when the Bot should use the entry, such as “Use for work purchases”, and the Bot follows the hint when it picks between entries (Cursor Help).

You can also save from a chat (Cursor Help):

  • When a Bot asks for a login, card or address with a Secure Form, check Securely save to Bot’s vault. If you leave it unchecked, the value is kept only for that chat and expires on its own.
  • When you attach a photo of a card, Grok Bot offers Save to Vault.

Importing logins from a password manager

On desktop, you can import logins from a CSV export from 1Password, Chrome or Edge, Safari or Apple Passwords, Firefox, Bitwarden or LastPass (Cursor Help):

  1. Export your passwords as a CSV file from the password manager:
    • 1Password 8: on a Mac, File > Export; on Windows or Linux, the ellipsis at the top of the sidebar, then Export. Pick the CSV format. 1Password’s CSV holds only Login and Password items, without custom fields such as security questions or backup codes (1Password Support).
    • Chrome: More > Passwords and autofill > Google Password Manager > Settings, then Download file next to “Export Passwords” (Chrome Help).
    • Bitwarden: in the web app, Tools > Export, then pick .csv as the file format. Bitwarden says only its .json exports include cards, so a CSV carries logins and notes (Bitwarden Help).
  2. In Settings > Vault, choose New item, then Import from CSV….
  3. Select Choose CSV file. The help page says the file is read on your computer and never uploaded, and it must be under 5 MB.
  4. Review the list. Items already in your vault are skipped. Rows with an error, 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.

LastPass exports bring cards too. The help page notes the CSV holds your passwords unencrypted and says to delete it once the import finishes (Cursor Help).

How to edit or remove an item

Open Settings > Vault and select the item to edit it, or choose Remove to delete it (Cursor Help). After you remove a login, Grok Bot can no longer sign in to that site with it. After you remove a card, it can no longer pay with it.

Limits the help page lists (Cursor Help):

  • To change a card’s number, remove the card and add it again.
  • On the phone, saved cards can’t be edited yet.
  • Passwords, usernames, websites, card numbers and security codes change only in Settings > Vault. Logins and cards are removed only there.
  • A Bot can change contact info, and an entry’s nickname and hints, when you ask it to.

Saved values are write-only. Passwords stay hidden in Vault, and cards show only their last four digits. You cannot read a saved value back (Cursor Help).

How the Bot uses Vault

The help page describes four cases (Cursor Help):

  • Signing in. The Bot uses a saved login first, then a connected password manager such as 1Password. If neither has the login, it asks you with a Secure Form.
  • New accounts. If you let the Bot pick the password when it signs up for a site, Vault generates the password and saves the login. The Bot never sees it.
  • Checkout. Saved cards fill in at checkout without the Bot asking each time. Contact info fills in shipping and billing details. Which other agents can shop and pay for you is on its own page.
  • Details you share in chat. When you give a Bot a name, address, phone number or email, it saves it as contact info once the task is done and tells you what it saved. Tell it if you don’t want something kept.

When a value is filled, the card in chat says Filled into the page. Secret values were never shown to your Bot. If it says Could not fill into the page, the page may have moved; the help page says the value was still not shown to the Bot (Cursor Help).

Vault doesn’t remove every hand-off. xAI’s docs say the Bot hands you the computer when a form can’t do the step, such as single sign-on, a passkey, a CAPTCHA it couldn’t get past, an approval on another device, a QR code or a bank card verification: choose Take over on the request, or open the computer and choose Take control, complete only that step, then choose I’m done and tell the Bot to continue (xAI Docs). The signed-in session stays on the computer for later tasks and is shared across your Bots. xAI doesn’t document how Vault fill-in and two-factor prompts interact on a given site. How that take-over step compares with other agents at a bank login is in can an AI agent log into your bank?

Approvals and Auto-review

The 0.75.5 release is titled “Vault, email forwarding, and fewer approval cards” (xAI changelog). The same release lets Bots forward an email from their own inbox with its original formatting, images and attachments, also requiring 0.75.2 or later.

Approval controls are in xAI’s docs (xAI Docs):

  • An approval card offers Allow once, Always allow (which can save a matching rule) and Deny.
  • Rules live in Settings → General → Auto-review. Ask first rules always stop matching actions. Allow automatically rules let matching actions proceed only when the automated review finds no other reason to stop. If both match, Ask first wins.
  • An approval from work that started without you, such as a routine, expires after 30 minutes and the action does not run.
  • Personal rules are saved to your account and apply on every desktop and the mobile app.

xAI lists purchases and financial transfers among the actions to keep behind explicit boundaries, and calls Auto Review “model-based” and a complement to, not a replacement for, explicit approval (xAI Docs). A narrow Ask first rule for purchases is one way to apply that. xAI doesn’t document a Vault-specific approval setting; a saved card fills in without a separate approval each time. Auto Review sits next to other vendors’ defenses against hidden instructions in our prompt injection guide.

What xAI says about storage and security

  • The Bot never sees saved passwords, card numbers or security codes, and Grok Bot does not show a saved value again (Cursor Help).
  • The Grok Bot page says “Your cloud computer is encrypted in transit and at rest” (xAI). That statement is about the cloud computer. xAI doesn’t publish where Vault items are stored or how Vault itself is encrypted.
  • All your Bots share one cloud computer, including browser sessions and logins, and xAI says not to use separate Bots as a security boundary (xAI Docs FAQ). Vault works the same way: everything you save is available to every Bot on your account, and you can’t limit an item to one Bot; Hints only guide which entry a Bot picks (xAI Docs).
  • Grok Bot uses Cursor account and data settings and does not support Legacy Privacy Mode (xAI Docs).

For how other agents handle the same risk, see AI agents, passwords and payments and the Grok Bot safety page.

Which plans include Grok Bot

The Grok Bot page says it is included with Premium ($30/month), Super ($100/month), Ultra ($200/month), Teams and Enterprise (xAI). xAI doesn’t say Vault differs by plan. The help page says Vault isn’t supported on shared Bots (Cursor Help), and the 0.78.1 changelog (Oct 27, 2026) says managers can add logins to a Team Bot’s own Vault in Configure, under Tools, so the Bot signs in with them for the team (xAI changelog). Current status and plans are on the Grok Bot page, and those prices next to other agents’ are on what AI agents really cost; install and first Bot are in how to get started with Grok Bot.

Related: Choosing between Grok Bot and Claude Duet? Here is the side-by-side comparison.

Sources

10 pages
  1. Cursor Help: Store secrets securely (Grok Bot) cursor.com
  2. xAI: Grok Bot changelog x.ai
  3. xAI Docs: Approvals, security, and privacy docs.x.ai
  4. xAI Docs: Vault docs.x.ai
  5. xAI Docs: Grok Bot FAQ docs.x.ai
  6. xAI: Grok Bot x.ai
  7. xAI Docs: Use the computer and apps docs.x.ai
  8. 1Password Support: How to export your data from the 1Password apps support.1password.com
  9. Google Chrome Help: Manage passwords in Chrome support.google.com
  10. Bitwarden Help: Export vault data bitwarden.com

Spotted something wrong or out of date? Report an error · Corrections log