Grok Bot version 0.75.5, dated October 23, 2026 on the official changelog, adds a Vault where users can save logins, payment cards and contact details for bots to use at sign-in and checkout. The feature needs Grok Bot 0.75.2 or later. Help docs place Vault under Settings on desktop and phone.
Key Facts
| Details | |
|---|---|
| Release | Grok Bot v0.75.5, October 23, 2026 (changelog also folds in 0.75.3 and 0.75.4) |
| Where | Settings > Vault |
| What you can save | Logins (site, username/email, password); cards (number, expiry, CVV, name, billing address); contact info (names, addresses, phones, emails) |
| What bots use it for | Sign-in and checkout form fill |
| Minimum app version | 0.75.2 or later |
| What the Bot can see | Contact info and which logins you saved; not saved passwords, card numbers, or security codes |
| Scope | Account-wide: every Bot on the account can use Vault items; not limited to one Bot |
| Team Bots | Vault is not supported; use Secrets for API keys instead |
| Checkout approval | Saving a card lets bots fill it at checkout; there is no setting that requires approval every time a saved card is used |
Background
The changelog lists Vault under New features alongside email forwarding and fewer Auto-review approval cards. Cursor's Grok Bot help page on secrets explains how to add items in Settings, import logins from a CSV export of common password managers, and optionally save from a Secure Form in chat by checking "Securely save to Bot's vault".
For API keys and other non-login secrets, the same help page points to the secure secret card (and Team Bot Secrets), not Vault. After a secret is saved, Grok Bot does not show the value again.
Secondary write-ups such as The Daily Bot summarise the same changelog points; product behaviour in this story follows the x.ai changelog and Cursor help docs.
What We Don't Know Yet
- Whether enterprise admins can disable Vault or audit Vault fills beyond existing product controls.
- How Vault interacts with a connected 1Password account when both have a login for the same site, beyond the documented order (Vault login first, then connected password manager, then Secure Form).
- Phone-side editing limits for saved cards beyond the help note that cards cannot be edited on phone yet (remove and re-add on desktop).