Grok Bot Can Now Keep Your Passwords and Cards in a Vault. The Changelog Does Not Say Whether Vault Entries Are Per-Bot or Shared.
Grok Bot v0.75.5, shipped October 23, adds a Vault for logins, cards, and contact details that Bots fill to sign in or check out, lets Auto-review send the emails and Slack messages you explicitly asked for, and raises routine caps to 300 runs an hour. The changelog says a Vault, singular, and does not say whether entries are scoped per Bot or shared across the one computer every Bot already shares. Three days earlier SpaceX told investors Grok Bot has 800,000 paid weekly users, on a call and not in the filing, with no definition. We read the changelog, the SEC exhibit, and the call coverage.
By T.W. Ghost
In August we wrote that Grok Bot wants your passwords, because every Bot on your account shares one cloud computer and its logins, and xAI's own docs said not to treat separate Bots as a security boundary. Two weeks ago we noted that the shared-computer line was still in the docs. Today, October 23, 2026, Grok Bot v0.75.5 gave the Bots somewhere to keep the passwords: a Vault.
The changelog entry is short. Bots can save logins, cards, and contact information to "a Vault in Settings" and fill them to sign in or check out. Emails and Slack messages you explicitly ask a Bot to send now go out once Auto-review allows them, while sends on routine and other turns still wait as drafts. The routine cap rises from 100 to 300 runs an hour in total, with up to 200 per routine. And the sentence that is not there: whether a Vault entry belongs to one Bot or to all of them.
The same week, SpaceX gave Grok Bot its first public user number, and the number has the same problem as the Vault: it is real, and it is undefined. We read the changelog, SpaceX's SEC exhibit, the call coverage, and the Business Insider account of the one Grok Bot incident on the record. Here is what held up.
What v0.75.5 Changes
| Grok Bot v0.75.5 (October 23, 2026) | |
|---|---|
| Vault | Save logins, cards, and contact info in Settings; Bots fill them to sign in or check out; requires v0.75.2 or later |
| Vault scoping | Not stated: "a Vault," singular; per-Bot or shared is not specified |
| Vault encryption and storage | Not stated in the changelog |
| Auto-review | "Emails and Slack messages you ask a Bot to send go out once Auto-review allows them, while sends on routine and other turns still wait as drafts." |
| Routines | Up to 300 runs per hour total (was 100); up to 200 per routine |
| Forward email with original formatting, images, and attachments | |
| Earlier this week, v0.75.2 (Oct 22) | Pages (reports, memos, dashboards; shareable with org and team controls), video creation, Shop Pay, X Money one-tap |
Scoping is the question, and we will not answer it for xAI. The August catch was structural: one computer, one set of logins, every Bot. A Vault that is shared across that roster is a convenience for the same exposure; a Vault scoped per Bot would be a real change. The changelog's wording supports neither reading, and the docs at the time of writing do not settle it. Re-read the live Grok Bot docs before you store anything.
Auto-review now sends. Until today, messages waited as drafts. Now the ones you explicitly asked for go out when Auto-review clears them; routine-triggered sends still draft. That narrows the human-in-the-loop by exactly the category of message a user is most likely to have asked for in a hurry.
800,000 Paid Weekly Users, Said on a Call
On SpaceX's third-quarter call on October 20, Gwynne Shotwell said Grok Bot had "paid weekly users of 800,000 earlier this month, more than doubling over the last month," per the transcript as carried by TSN. Elon Musk spoke of wide enterprise deployment "within a few weeks" and of Grok Bot possibly using most of the company's SI compute. The SEC 8-K and its Exhibit 99.1 name Grok Bot as an AI revenue driver and print no user count at all. "Paid weekly user" is not defined in any of the materials we read, and no prior baseline is given for the doubling.
So: quote Shotwell for 800,000, quote the filing for "named, no number," and do not put the figure in the 8-K's mouth. The Pages feature in v0.75.2, with public share links, expanded Grok Bot's sharing surface in the same week.
The One Incident on the Record
Business Insider published an as-told-to on October 9 with Shane Mac, CEO of XMTP Labs, who described a Grok Bot "personal CFO" that posted his personal bank balances into his company's Slack after confusing similarly named channels. Mac said Grok investigated and shipped a fix that requires explicit permission before an agent moves information to other channels. That is a channel-permission fix. It is not a change to the shared computer, and it is the clearest illustration yet of why Vault scoping is the question that matters. SpaceXSI has not published its own account.
Verified vs Unconfirmed: The Scorecard
| Claim | Verdict |
|---|---|
| v0.75.5 Oct 23: Vault for logins, cards, contact info; Bots fill to sign in or check out | Verified (Grok Bot changelog) |
| Auto-review sends explicitly requested emails and Slack messages; routine sends still draft | Verified (changelog, quoted) |
| Routine caps 300 per hour total, 200 per routine | Verified (changelog) |
| Vault entries per-Bot or shared | Unverified (changelog says "a Vault"; scoping not stated) |
| Vault encryption details | Unverified (not in the changelog) |
| Shotwell: 800,000 paid weekly users, more than doubled in a month | Press and transcript (TSN); not in the 8-K |
| 8-K names Grok Bot as a revenue driver with no user count | Verified (SEC exhibit) |
| Definition of "paid weekly user"; prior baseline | Unverified (not published) |
| Shane Mac bank-balance incident and channel-permission fix | Press, subject's own account (Business Insider, Oct 9); not confirmed by SpaceXSI |
Who Should Use It
Use the Vault for the logins you would already have typed into a Bot's browser session, after you have read the live docs on scoping and encryption, and only for accounts whose terms allow an agent to log in; US banks are blocking exactly this pattern this week.
Skip it for bank credentials until both the bank's terms and the Vault's scoping are clear, and expect Auto-review to send the messages you asked for without a draft step from now on.
The frontier is elsewhere: Grok Bot's user number is now public and undefined, and its security model is now more convenient and no better documented. Our model comparison has the current standings side by side.
Sources
- Grok Bot changelog
- TSN: SpaceX says Grok Bot has 800,000 paid weekly users
- Business Insider: a personal AI agent posted bank details into a company Slack
*Not sure which agent should hold which credential, if any? Take the free 2-minute quiz and get matched. Then read what the banks did about it the day before: US banks are blocking credential-based agents.*