Grok Bot's Vault lets Bots sign in and pay without seeing your passwords
1 day ago
Grok Bot's Vault holds your logins, cards and contact info so your Bots sign in and check out without seeing your passwords. Also: the sign-in order, what a Bot can edit, paying with a saved card, importing logins, deleting a Bot, and the team-size rule for Team Bots. https://docs.x.ai/grok-bot/vault https://docs.x.ai/grok-bot/computer-and-apps https://docs.x.ai/grok-bot/how-grok-bot-works https://docs.x.ai/grok-bot/settings-and-notifications https://docs.x.ai/grok-bot/bots https://docs.x.ai/grok-bot/team-bots
Ask about this presentation
Chapters
Show transcriptHide transcript
Grok Bot's Vault keeps your logins, cards and contact info, so your Bots can sign in and check out for you. It's under Settings, and needs Grok Bot 0.75.2 or later.
A Bot never sees a saved password, only which logins you saved, plus your contact info. In Grok Bot app chats it also sees a card's number and code, to type in after you tap Pay.
To sign in, a Bot tries Vault, then a connected password manager like 1Password, then asks you with a Secure Form. It finds emailed one-time codes in Gmail, Outlook or its own inbox.
A Bot can update your address when you ask, and a card's details in app chats. Passwords, usernames and websites change only in Settings, and only you remove a login or card.
A card saved in Vault fills in at checkout without asking you first. To approve every purchase, leave the card unsaved. Bots can also pay with Link, X Money or Shop Pay.
On desktop, Vault imports a CSV export from 1Password, Chrome, Safari, Bitwarden and others. The file stays on your computer. Delete the export afterward, because it holds your passwords unencrypted.
Deleting a Bot erases its memory, routines and conversations, plus any template you shared from it, so that link stops working. Files and sign-ins on the shared computer can stay behind, so clean those up yourself.
If you're the only person on your Cursor team, you can't create or share a Team Bot until a teammate joins. Your personal Bots aren't affected.
If your Bots sign in for you, I'd move those logins into Vault, and keep a card out if you want to approve each purchase. The full guide is Vault and secure sign-in.
Up next
1:06Grok Bot now acts only as you, and keeps your passwords out of the model
@grok-bot
1 day ago
2:29Grok Bot now signs in with Okta FastPass on its own computers
@grok-bot
2 days ago
2:19Grok Bot now shares one Bot with your whole team, in Slack and Teams
@grok-bot
2 days ago
1:59Grok Bot Team Bots now learn for the team and join Microsoft Teams
@grok-bot
3 days ago
1:56Grok Bot buys your conference pass from memory and asks before it emails finance
@grok-bot
1 week ago
1:04Grok Bot now shuts idle computers after 30 days without a message
@grok-bot
1 week ago
2:17Grok Bot inference hooks let your security server block a prompt before the model sees it
@grok-bot
3 weeks ago
1:58Grok Bot admins can now wipe a member's Bots and data in one step
@grok-bot
3 weeks ago
1:47Grok Bot lets Enterprise team admins recreate or terminate Bot computers in bulk
@grok-bot
1 month ago
2:52Grok Bot now deploys to your whole organization with Jamf, Intune and Ansible
@grok-bot
1 month ago
1:19Grok Bot plugins now install from Connect apps
@grok-bot
1 month ago
1:43Grok Bot Team Bots get managers, and Bots can read X
@grok-bot
1 month ago









