Grok Bot 0.75.5: Introducing The Vault, Smarter Approvals, and Email Forwarding

0:08 Welcome to Grok Bot Release Notes, brought to you by Jellypod AI. Today it's Grok Bot 0.75.5, which shipped Friday, October 23, 2026. Eric Zakariasson announced it on X as stable and rolling out, and it's in the official changelog feed. It also bundles 0.75.3 and 0.75.4, so you're getting three releases in one.

0:31 One quick note on sources. The community changelog at getgrokbot.com says it was last updated August 31, so it's behind. The official x.ai feed and Eric's post are the record for this episode. This one connects to the last episode. In 0.75.2 we covered live Pages, video creation, Shop Pay and X Money, and memory across chats.

0:53 That release let a Bot browse and buy. 0.75.5 is about making that practical. And several of its headline features say plainly that they require Grok Bot 0.75.2 or later, so update first. Start with the big one, the Vault. In Settings, a Bot can now save your logins, cards, and contact info, then fill them in to sign in or check out.

1:14 Think about what happened before. If a Bot hit a login wall, it handed you its computer so you could type your password yourself. That's safe, but it breaks the point of a Bot that keeps working while you're away. The Vault is meant to remove that interruption for routine sign ins and purchases. People noticed.

1:32 One reply to the announcement said, quote, "i have been dying for the vault." Another called it huge. Now the caution, and this part is interpretation backed by a community cheat sheet, not the changelog. That cheat sheet says every Bot on your account shares one cloud computer, with the same files, browser sessions, and credentials.

1:51 It says separating Bots is not a security boundary. So when you put a card or a login in the Vault, think of it as something your whole Bot setup could be near. Only save what you're comfortable with, and keep your approval rules on.

2:04Second feature email forwarding.

2:06 Bots can forward an email from their own inbox with its original formatting, images, and attachments. The changelog doesn't tell us what happened before, so I won't guess. What it does tell us is what you get now. If a vendor sends a formatted invoice with a PDF attached, the Bot can pass along that email with the formatting and attachment, rather than you having to rebuild it.

2:27 That also requires 0.75.2 or later.

2:31Third Slack.

2:32 Bots now record who asked for each message they post, so anyone in the thread can ask who requested it. If several teammates share a Bot, that's a simple audit trail, and it answers the question of who told the Bot to say that. And for Halloween, you can give a Bot a pumpkin shape when you create it or change its avatar.

2:51 That one also requires 0.75.2 or later. Small, but fun. Now the part I think matters most day to day: approvals. A Bot that asks permission for everything gets ignored, and a Bot that never asks is risky. This release tunes the middle. First, Auto review asks less often for an action you asked for in your own words.

3:12 If you tell the Bot directly to do something, it should stop interrupting you with a card about it. Second, when you deny an approval card, the Bot stops. It doesn't try that action again until you send another message. So denying is now a real stop button, not a suggestion. Third, sending. Emails and Slack messages you ask a Bot to send go out once Auto review allows them.

3:34 But sends on routine and other turns still wait as drafts. So a message you explicitly requested goes out, while a scheduled run still pauses for your review. That's a sensible split. There are also two fixes. Auto review now retries a check that fails, and reviews long chats instead of stopping, so it falls back to an approval card less often.

3:55 And it no longer waves through an action your request said to stop before. The changelog's example is sending a message you asked only to draft. That one's a real safety fix. If you say draft only, it means draft only. Next, routines. Your routines can now run up to 300 times an hour in total, up from 100, and each routine can run up to 200 times.

4:18 If you use routines to watch an inbox or react to events, you have a lot more headroom. Keep in mind those are ceilings, not a promise that every workflow should run that often. A few connector changes are worth knowing. When a Bot hands you its computer to sign in to a site that has a connector, it also offers that connector's connect card, so you can choose the cleaner route.

4:39 Asking a Bot about your X account now connects X through your linked account, even if you removed the X plugin. Connecting X also connects X Money through the same account, and asking about your X Money balance, activity, or card installs it. Plugins with several servers, such as Salesforce, now show each server as its own row, so you can see and sign in to every one.

5:01 On networking, if you turn on Route traffic through this computer, Settings now shows how many sites were blocked because they resolve to a private or VPN address. It's a counter, but it gives you visibility into what's being stopped. For teams, teammates in their own DM with a Team Bot can now react to messages, quote with Add to chat, and answer cards.

5:21 And when a Team Bot's routine replies in a Slack thread, the Bot follows the thread and answers later replies without an @mention. A few smaller fixes. After an account merge, you keep managing the Bots you created and can share them with your team. In Slack, Bots now answer thread replies that were also sent to the channel.

5:40 And if you ask a Bot about your X followers, you get a plain answer that X doesn't offer it, instead of a browser sign in. So how do you use this? Here's a workflow that's my own suggestion, not from the release notes. Give a Bot a finance or ops job. Save only the logins it truly needs in the Vault.

5:58 Have it watch an inbox, forward vendor invoices with attachments to your accounting contact, and post a summary in Slack. With the new attribution, your team can see who asked for each post. Keep routine sends as drafts until you trust the output. For context, xAI has published its own write ups of using Grok Bot on procurement and incident response, if you want ideas.

6:19 One last thing. A tracker account on X flagged a 0.75.8 build on October 24th, but it says its notes are AI generated and that the official changelog doesn't list it. So treat that as unconfirmed. Update to 0.75.5, make sure you're on 0.75.2 or later, and check your approval settings. Thanks for listening, and thanks again to Jellypod AI for bringing you this episode.