Grok Bot Vault: An AI Agent That Uses Your Logins Without Seeing Them

On October 23, the official Grok Bot account announced that the assistant "can now save your logins, cards, and contact information," so you add them once and it remembers them for later. TestingCatalog reported that saved items live in a new Vault tab in settings and that the feature is rolling out on the mobile and desktop apps. Elon Musk shared it too, summing it up as "Grok @Bot saves sensitive info in a vault."

I'll be honest: this is the kind of feature I've been waiting for. I spend a lot of my time wiring systems together, and the hard part of any automation is never the logic. It's the credentials. Who holds them, where they live, and what can see them. An AI assistant that can log in and buy things raises that question in the loudest possible way. Vault is a genuinely thoughtful answer to it.

According to Grok Bot's help page on storing secrets, Vault holds three kinds of things:

• Logins: a website, a username or email, and a password. The Bot uses a saved login to sign in on that website.
• Cards: number, expiry, security code, name on card and billing address.
• Contact info: names, addresses, phone numbers and emails for shipping and billing.

You can add items yourself in Settings > Vault, or save them from a chat. When the Bot asks for a login, card or address with a Secure Form, there's a "Securely save to Bot's vault" checkbox. Leave it unchecked and the value is kept only for that chat and expires on its own. There's also a hints field, like "Use for work purchases," that tells the Bot which entry to pick. On desktop, you can import logins from a CSV export from several popular password managers and browsers.

Here's the design choice that makes this work. When you type a password or card number into one of these secure forms, it doesn't go into the conversation. The help docs put it plainly: "Your Bot never sees a saved password, card number, or security code." Saved values are write-only. In settings, passwords stay hidden and cards show only their last four digits.

So how does the Bot sign in if it can't see the password? It doesn't need to. It can see which logins you've saved, so it picks the right entry, and the secret gets filled straight into the web page without passing through the AI. In the announcement video, the secure form for a sign-in even notes the password is "Never shown to your Bot. Only filled on" the site it belongs to.

Why does that matter so much? Anything an AI model reads becomes part of what it's working with. Keeping the secret out of that context entirely means it can't be repeated back, logged in a transcript, or talked out of the assistant by a sneaky web page. It's the same principle good developers use with API keys: the code that needs the key gets it, and nothing else does.

A few other details I liked:

• It asks before paying. Saved cards fill in at checkout, and the docs say the Bot asks before it uses one.
• It can make passwords it never sees. If you let it pick a password when signing up for a site, Vault generates it and saves the login.
• The important stuff stays in your hands. The Bot can update contact info and an entry's hints when you ask. Passwords, card numbers and security codes change only in Settings > Vault, and logins and cards are removed only there.

One thing to know going in: contact info is not hidden from the Bot. It can see your saved names, addresses, phones and emails so it can type them into forms. That's by design, and it's worth knowing before you save anything.

If you run a small business, an assistant that can reorder supplies, pay a vendor or pull a report from a portal is a real time-saver. Grok Bot's own security and approvals docs recommend a least-privilege setup, and that matches what I'd tell any client. Here's how I'd approach it:

• Give it its own logins where you can. Many business tools let you add a separate user with limited permissions. Use that instead of the owner account, so the assistant can only reach what the job needs.
• Use a separate card with a low limit. A dedicated card, or a virtual card if your bank offers one, keeps any mistake small and easy to spot on a statement.
• Keep 2FA on. Two-factor authentication still matters. The docs say that for passwords, passkeys, two-factor codes, CAPTCHAs and payment confirmations, the Bot should hand control of the computer back to you to finish that step.
• Keep a dedicated password manager as your source of truth. I use one for everything, and I'd treat Vault as the set of logins the assistant needs, not a copy of every password you own.
• Review before anything is bought or sent. Set clear limits in your request, like "find it and put it in the cart, but don't check out." The docs list purchases, sending messages and deleting data as actions worth keeping behind approval.
• Use hints. A hint like "Use for office supplies only" keeps the right card on the right job.
• Clean up. When an employee leaves or a project ends, remove the matching logins and cards in Settings > Vault and change the passwords at the source.
• Never paste secrets into chat. The docs are clear on this. Use the secure form or Vault instead.

This feels like a milestone for AI assistants. Letting an AI handle logins and payments has always sounded either magical or reckless, depending on who you ask. Vault makes the case for magical by keeping the most sensitive values away from the AI completely while still letting it do the work.

It's still new, so I'd start small: one login and one low-limit card, and watch the first few runs. I plan to try it on low-stakes tasks first and will share what I learn.

If you're thinking about bringing AI automation into your business and want help setting it up safely, with the right permissions, separate accounts and approvals, send me a note or email caleb@calebdorris.com.

Can Grok Bot see my saved passwords or card numbers?

No. Per the official help docs, the Bot never sees a saved password, card number or security code. It can see your contact info and which logins you've saved, so it can choose the right entry.

Where do I find Vault?

In Settings > Vault, on desktop and on the phone. TestingCatalog reported the feature is rolling out on the mobile and desktop apps, so you may not see it right away.

Will it buy something without asking?

The docs say the Bot asks before it uses a saved card at checkout. It's still smart to state your limits in the request.

Does it work on Team Bots?

Not yet. The help docs say Vault isn't supported on Team Bots, which use a separate Secrets feature for API keys.

• Grok Bot (@bot) on X, Vault announcement, Oct. 23, 2026
• TestingCatalog on X, Vault tab rolling out on mobile and desktop
• Elon Musk on X, "Grok @Bot saves sensitive info in a vault"
• Grok Bot Help, Store secrets securely
• Grok Bot Docs, Approvals, security, and privacy