Grok Bot Adds a Vault for Logins and Cards

Grok Bot can now keep a user’s logins, payment cards and contact details in a Vault and fill them in when it signs in to a site or checks out, according to the product’s official changelog. The feature arrived in version 0.75.5, dated 23 October. The same release forwards emails with their attachments, cuts the number of Auto-review prompts and raises the limit on scheduled routines.

The official @bot account announced the Vault at 20:43 BST on Friday: “Grok Bot can now save your logins, cards, and contact information. Add them once, and Bot securely remembers them for the future.” Elon Musk quote-posted the announcement early on Saturday, writing: “Grok @Bot saves sensitive info in a vault”. TSN follows Grok Bot and Musk’s other businesses on its Musk Companies hub.

The Vault lives in Settings and needs version 0.75.2

The changelog describes the feature in two sentences: “Bots can save your logins, cards, and contact info to a Vault in Settings and fill them in to sign in or check out. Requires Grok Bot 0.75.2 or later.”

That is all the detail the company has given. Neither the changelog nor the @bot post says how the Vault stores or protects what is saved. “Securely” is the company’s own word, and no independent review has been published.

Before this release, the changelog described the Bot collecting such details as it needed them. Its 14 October entry says that “at checkout, Bots use card details or photos you send in chat, asking only for missing fields or a verification code in a Secure Form”, and that “Bots ask for logins and other multi-field details on one Secure Form”. Mac users have been able to connect 1Password from the Marketplace since September so the Bot can use saved logins, “asking you first unless you turn on Auto fill”, the changelog says.

On 22 October the @bot account said a wider 1Password integration was “rolling out to users over the next few days”. The same day, 1Password launched 1Password for Agents and named Grok Bot as a launch partner. The service fills a credential “directly into the sign-in form instead of sending it to the agent”, 1Password said in its release. The Vault gives users a second option inside Grok Bot itself. TSN’s guide to booking a flight with Grok Bot explains how checkout approvals work.

Forwarded emails now keep their attachments

Bots have had their own email addresses since 11 October, according to the changelog. Version 0.75.5 lets them pass messages on intact: “Bots can forward an email from their own inbox with its original formatting, images, and attachments,” the changelog says. Like the Vault, this needs version 0.75.2 or later.

In Slack, the Bot now keeps a record of who asked for each message it posts, “so anyone in the thread can ask who requested it”. Both changes add to a run of releases that have pushed the Bot towards office work, such as building reports, memos and dashboards.

Auto-review should ask for approval less often

Several changes target Auto-review, the check that decides whether the Bot can go ahead with an action or must show the user an approval card. “Auto-review asks less often for an action you asked for in your own words,” the changelog says, and it “falls back to an approval card less often, retrying a check that fails and reviewing long chats instead of stopping.”

Other changes tighten it. “After you deny an approval card, the Bot stops and doesn’t try that action again until you send another message.” Auto-review also “no longer waves through an action your request said to stop before, such as sending a message you asked only to draft.” Emails and Slack messages a user asks the Bot to send “go out once Auto-review allows them, while sends on routine and other turns still wait as drafts.”

Routines can now run 300 times an hour

Scheduled routines get more room. “Your routines can run up to 300 times an hour in total instead of 100, and each routine up to 200 times,” the changelog says. That follows an update earlier this month in which the company claimed faster computer tasks and added X Chat and new connectors.

Stored cards make approval rules carry more weight

The Vault removes a step that used to protect users almost by default. When the Bot had to collect a card number or password in chat or through a Secure Form, the user handed over the details at the moment they were needed. With details saved in advance, that step disappears, and the user’s protection rests on two things the company has described only briefly: how the Vault keeps data safe, and how Auto-review decides when to stop and ask.

The rest of the release reads in that light. Fewer approval prompts will be welcome to anyone tired of confirming the obvious. But the release also says the Bot will now stop after a denied card and will no longer wave through a send that a user asked only to draft. Those are the kinds of controls that matter more once the Bot can pay without being handed a card each time. Routine-driven sends still wait as drafts.

Users choosing between the Vault and the 1Password route face a trade-off the sources leave open. 1Password says its service keeps the credential away from the agent. The changelog says only that the Bot fills Vault details in. Until the company publishes more on storage and access, the Vault is best judged on the description given, not on the word “securely”.

Grok Bot Adds a Vault to Save Logins, Cards and Contact Details

The Vault lives in Settings and needs version 0.75.2

Forwarded emails now keep their attachments

Auto-review should ask for approval less often

Routines can now run 300 times an hour

Stored cards make approval rules carry more weight

Sources

Related stories

AI-Guided Lab Finds Hydrogen Catalysts It Calls Comparable to Platinum

Meta Buys Sundial as Two Ex-Meta Founders Return for AI Analytics

AWS Open-Sources Infinity, Saying 75,000 Idle AI Agents Fit in 8GB

Figure Says Its Figure 04 Humanoid Has Reached Design Lock

Latest stories