Vault and secure login: Let the Bot log in for you, without seeing your password

One-sentence goal: Store logins, bank cards, and contacts in Grok Bot Vault, so the Bot can log in to websites, fill forms, and make payments for you, while never seeing your passwords or card numbers.

Preparation

• Grok Bot 0.75.2 or later; Vault is available starting from this version.
• Either the desktop client or the mobile app works; the entry point is under Settings → Vault.
• First finish"Connecting apps (plugins): How to connect Gmail, Slack, and calendar".
• Remember two boundaries: Vault is account-level, and saved content is visible to all Bots under the account—you cannot restrict a credential to a single Bot; shared Bots do not support Vault, so use Secrets (environment variables) instead to pass them keys.
• The Bot cannot see passwords, card numbers, or security codes, but it can see contact information and "which logins you have saved," which is used to pick entries and fill forms on your behalf.

Follow along

Step 1: Create a Vault entry

Open Settings → Vault, click New item, and choose one of Login, Card, or Contact info:

• Login: Fill in Website, Username or email, and Password, then click Save login.
• Card: Click Scan with camera or Upload a photo to auto-recognize from a card photo, or manually fill in the card number, expiration date, security code, cardholder name, and billing address, then click Save card.
• Contact info: Fill in name, address, phone, and email, then click Save contact info.

Expected result: The entry appears in the Vault list, the password stays hidden, and the card number shows only the last four digits.

Step 2: Use Hints to tell the Bot when to use it

Write the usage scenario in the entry's Hints, for example, "Use this card for work purchases." When multiple entries match, the Bot picks based on the hints.

Expected result: When you have multiple cards or accounts, the Bot picks exactly the one you want it to use.

Step 3: Have the Bot log in, or save conveniently via Secure Form

In chat, directly ask the Bot to log in to a website. The Bot retrieves credentials in this order: Vault first, then 1Password, and finally Secure Form. If the Bot asks for your account and password via Secure Form, check Securely save to Bot's vault and this input will be stored in Vault; if left unchecked, it is only valid for the current session and expires automatically.

Expected result: The Bot opens the website, auto-fills the credentials, and completes the login; the next time it logs in to the same website, it reuses the Vault entry directly without asking you again.

Verify

1. Have the Bot log in to a website with a saved Login: it should get into the account, and your password should never appear in the chat.
2. Go back to Settings → Vault and confirm the entry exists and the values are hidden.
3. Official reminder: after saving, Grok Bot will no longer display plaintext values, and seeing blank fields afterward does not prove the key has been deleted.

Common pitfalls

• Version too old: Versions below 0.75.2 have no Vault—upgrade the client first.
• Wanting to isolate credentials per Bot: Not possible—Vault is shared across the whole account, so think carefully before storing sensitive credentials.
• Can't find Vault in shared Bots: It is simply not supported; pass keys like API keys via Secrets.
• Pasting API keys into chat: Don't. Use a secure secret card for key-type content—the value will be masked when displayed.
• Bulk migration (desktop only): In Settings → Vault, click New item, select Import from CSV…, then click Choose CSV file and pick a CSV exported from 1Password, Chrome, Edge, Safari or Apple Passwords, Firefox, Bitwarden, or LastPass. The file must be smaller than 5 MB, is read only locally and never uploaded; existing entries are skipped, and rows missing a password or with a non-https website are not imported. The exported file is plaintext—delete it immediately after importing.
• Payment methods: Settings → Vault also has Payment accounts (connectable wallets, such as Link and X Money) and Default payment method (the payment method the Bot uses first).

Related: Approvals and Auto Review: Let the Bot act with confidence.

Next lesson

With the credentials ready, the next step is to let the Bot use your network and local computer to do the work: Traffic routing and local execution: letting the Bot use your network and computer.