Grok Bot's New Vault Can Save Your Cards for Every Bot. The Help Page Says There's No Setting That Makes It Ask Before It Pays.

Honest fence (read first): This is about a feature that shipped and is documented: Grok Bot's Vault, in version 0.75.5 on Friday, Oct 23. Everything below comes from SpaceXSI's own changelog, its help page and its official posts. We haven't independently tested how the Vault stores data, and SpaceXSI hasn't published a security review of it. Our Oct 20 post covered who pays when a Bot's purchase goes wrong. We won't argue that again here.

Editorial Thesis

The Vault solves a real annoyance. Until now, a Bot that hit a login page or a checkout either asked you for the details or stopped. Now you save them once and the Bot fills them in. The official post sells it simply: "Add them once, and Bot securely remembers them for the future."

The part worth slowing down for is a single answer on SpaceXSI's own help page. It asks, "Will my Bot ask before it uses a saved card?" and answers, "Not necessarily." Saving a card, it says, "lets your Bots fill it in at checkout, and there's no setting that requires your approval each time a saved card is used." Put that next to two other facts from the same week: the Vault covers every Bot on your account, and Grok Bot is now built to show you fewer approval cards. You get a much smoother checkout. Your control now depends on what you choose to save.

Honest Verdict

Proven (documented by SpaceXSI): the Vault exists, holds logins, cards and contact info, and the Bot "never sees a saved password, card number, or security code." Vault items work across every Bot on the account. There's no per-payment approval switch for saved cards. Claimed: "securely." The help page describes write-only storage, but there's no public audit, encryption detail or third-party review. Your call: whether you save a card at all. SpaceXSI's own advice, if you want to approve every payment, is don't.

What shipped, and when

The timeline comes from the official changelog (x.ai/changelog/bot, read Tue Oct 27 at 5:00 AM ET, latest version 0.75.8):

The official @bot account announced the Vault at 3:43 PM ET on Oct 23. Elon Musk quote-posted it that evening: "Grok @Bot saves sensitive info in a vault." Michael Truell (@mntruell) called it "Instant login and checkout with @Bot."

What the Bot can and can't see

This is the strongest part of the design, and the help page ("Store secrets securely") is specific about it:

• What it holds: logins (website, username or email, password), cards (number, expiry, security code, name, billing address), and contact info (names, addresses, phones, emails).
• What the Bot sees: "Your Bot never sees a saved password, card number, or security code. It can see your contact info and which logins you saved." The value gets filled into the page without being shown to the Bot.
• What you see: saved passwords stay hidden, and cards show only their last four digits. Saved values are "write-only." You can't read them back.
• New accounts: if you let the Bot pick a password when it signs up somewhere, "Vault generates the password and saves the login. Your Bot never sees it."

That's a sensible design. It keeps your secrets out of chat logs and out of the Bot's working memory, which is where they'd leak from in a bad session.

The three lines that matter for your wallet

1. It's account-wide. "Vault covers your whole account. Everything you save is available to every Bot on your account, and you can't limit an item to one Bot." If you've built a shopping Bot, a travel Bot and a research Bot, a card you save for one is usable by all three. Some users run dozens: Hiten Shah posted on Oct 22 that he'd made 81 since August.

2. There's no ask-first switch for saved cards. That's the "Not necessarily" answer above, quoted in full. The help page's fix is blunt: "If you want to approve each payment yourself, don't save the card." At checkout, leave Securely save to Bot's vault unchecked and the card is used only in that chat. It also warns: "A form without that checkbox saves straight to Vault, so don't submit it."

3. Approval cards are getting rarer on purpose. Since Oct 11 (v0.70.2), the changelog says that before an action it can't undo, "such as sending, posting, buying, or deleting, a Bot checks your own messages for approval." That's a check on what you said, not necessarily a card you tap. The Oct 23 and Oct 24 releases push the same way: fewer cards when your words already asked for the action, and emails and Slack messages you ask for "go out once Auto-review allows them." Sends from routines still wait as drafts.

Taken one at a time, each of these is reasonable. Taken together, a saved card, a vague request like "reorder the usual," and an Auto-review that reads your message as approval can add up to a purchase you didn't picture. That isn't a bug report. Nobody has shown it happening. It's just what the documented settings allow.

What SpaceXSI got right

To be fair to the design:

• Denials stick. "After you deny an approval card, the Bot stops and doesn't try that action again until you send another message" (v0.75.5).
• "Draft only" is respected. The same release fixed a case where Auto-review "waves through an action your request said to stop before, such as sending a message you asked only to draft."
• Import stays local. CSV imports from 1Password, Chrome, Edge, Safari, Firefox, Bitwarden or LastPass are "read on your computer and never uploaded" (under 5 MB). The page also tells you to delete the CSV afterward, because it "holds your passwords unencrypted."
• Removal is clean. Remove a card in Settings > Vault and "Grok Bot can no longer pay with it."

What we still can't verify

• How it's stored. "Securely" and "write-only" are SpaceXSI's words. We found no published encryption design, audit or bug-bounty scope for the Vault.
• Spend limits. The help page offers no per-card cap, per-Bot scope or merchant allowlist for Vault cards.
• How often Auto-review says yes. "Fewer approval cards" is SpaceXSI's description. There's no public data on how often it allows versus asks.
• Contact info you didn't mean to save. When you give the Bot a name, address, phone or email in chat, "it saves it as contact info once the task is done and tells you what it saved." That's useful, but it's opt-out ("Tell it if you don't want something kept").

A careful setup (from the documented options)

1. Save logins first, cards later. Logins carry less direct money risk, and the Bot still can't see the password.
2. If you save a card, use a low-limit or virtual card. That's a bank-side control, not a Grok Bot one, and it's the only spend cap you'll have.
3. Use Hints. Each Vault entry takes a hint such as "Use for work purchases," and the Bot "follows the hint when it picks between entries." A hint is guidance for the Bot, not a lock.
4. Want to approve every payment? Don't save the card. Leave the Secure Form box unchecked.
5. Be specific when you shop. "Buy this item, under $40, from this store" leaves Auto-review less to interpret than "get the usual."

The video

The embedded walkthrough is from Grok Bot Desk Signal, a small explainer channel, uploaded Saturday, Oct 24 (6:21). It's not an official SpaceXSI video. We found no official or major-outlet YouTube video on the Vault yet. SpaceXSI's own 19-second demo is on X only. Use it as a tour of the screens. The help page is the rulebook.

Bottom line

The Vault is a real, documented feature with a thoughtful core: your Bot uses your secrets without seeing them. The trade-off is also documented, in SpaceXSI's own words. Every Bot can use every saved card, and nothing makes it ask first. Decide what to save with that in mind.