
Grok Bot Gets a Main Bot and Faster Team Workflows
This episode breaks down the latest Grok Bot releases from 0.62.0 to 0.66.0, including the new Main Bot role, Slack approval cards, manager access for Team Bots, and the option to send messages without draft review. It also covers reliability fixes, automatic updates, and what the new official changelog means for tracking future changes.
Chapter 1
Five Releases in Five Days
James Turner
Last time, I told you SpaceXAI had no official per version changelog, and that getgrokbot.com stopped at August 31. That gap just closed. There's now an official Grok Bot feed at x.ai/changelog/bot, and it shows five releases between September 28 and October 2, 2026. Version 0.62.0 through 0.66.0. This episode is brought to you by Jellypod AI, the easiest platform to create AI podcasts and generative videos. We covered the Team Bots architecture, the memory split, and the billing last time, so I'll skip that and go straight to what's new.
James Turner
Start with the newest, version 0.66.0 from October 2. You can now choose a primary Bot, marked Main Bot with a star. Per the changelog, it checks in proactively and coordinates work with your other Bots. One condition matters here: it requires Grok Bot 0.59.0 or later. So if you're running an older copy, update first. The practical idea is simple. Instead of you bouncing between six specialist Bots, one of them becomes the front door. I'd pick the Bot that already knows the most about your priorities.
James Turner
Next, version 0.64.0 from September 30 added something you should treat carefully. Email and Slack draft cards now offer Disable drafts for this Bot. Turn that on and the Bot sends messages directly, with no review step. If you want drafts back, you ask the Bot to turn them on again. That's a real shift from approve first to act first. My take, and this is interpretation, not from the notes: only use it where a wrong message is cheap, like an internal status channel. Don't use it on a customer email.
James Turner
Version 0.63.0, September 29, is about approvals in Slack. When a Bot in a Slack thread needs your approval, it now posts a Review an action card that only you can answer, instead of dropping the action. You can also ask a Team Bot in Slack to message one of your own Bots, and the reply comes to you privately in Grok Bot. Both of those are tagged for Teams. The point is that a shared Bot in a shared channel can ask permission without anyone else being able to click yes for you.
James Turner
Also in 0.64.0, the creator of a published Team Bot can add teammates under Managers, who can change its profile, skills, plugins, secrets, and Slack app. That means the Bot doesn't depend on one person's availability. Avatars got a refresh with bigger eyes, plus square, sparkle, clover, flower, heart, house, and star shapes. And when a Bot needs a login or a form filled, a Secure Form window opens showing the site's name and icon, which makes it easier to check where you're typing a password.
James Turner
And the week opened with version 0.62.0 on September 28, which is a pile of everyday composer upgrades. Select text in a chat and press Cmd or Ctrl plus L, or choose Add to prompt, to quote it in your next message. Type a dash or one followed by a period to start a list, with Shift Enter adding an item, Tab nesting it, and Enter still sending. There's also spell check as you type, which you can turn off. A Bot's info pane also gets a Library tab listing pages, files, and links it has shared, grouped into Today, This week, and Older. For Team admins, the dashboard now lets you search Team Bots by Bot or creator name and delete a teammate's Team Bot.
Chapter 2
Fixes, Voice, and How to Use This
James Turner
Now the changes that affect how reliable this feels. Version 0.65.0 turned Automatic Updates on by default, so Grok Bot restarts to apply updates while you're away. If you don't want that, go to Settings, then Updates. Same release: your phone skips notifications for a Bot you're viewing on your computer, and resumes once the computer locks, sleeps, or sits idle. Teammates can also start a voice chat with a Team Bot, and that call stays in their own conversation. Team Bot setup now goes card to card, with labels like Step 2 of 5.
James Turner
The fixes might be the best part. In 0.66.0, a Bot that hangs on an unresponsive command or computer stops itself with a note, and your next message picks up where it left off. Phone notifications now fire once per Bot reply, and never for chats you've deleted. In 0.63.0, after a Bot says it's on your request and does the work, it now sends the result instead of going quiet. When you use up your plan's included usage, you see the usage limit notice instead of Bot failed to respond. Grok Bot also signs in on networks with a TLS inspecting proxy, using root certificates installed on your computer. And from 0.62.0, deleted Bots free their screens on the shared computer, so other Bots' browser actions stop failing because every screen is taken. Also, Gmail now sends to the recipients the Bot names, not a saved draft's original recipients.
James Turner
Outside the Bot itself, SpaceXAI's API docs show that Grok Voice Transcribe 1.0 reached end of life on October 2, with requests routed to Grok Voice Transcribe 2.0 at the same price, with higher accuracy. I want to be careful: the docs don't say Grok Bot uses that model, so any benefit to Bot voice chat is my inference. Same for Grok 4.7, which arrived September 21 on the API. I haven't seen a Grok Bot specific note about it, so I'm not promising anything there.
James Turner
For a sense of how people use these, the getgrokbot.com directory has two good examples. Lauren's dr eggbot designs Grok Bots and holds them to a bar of one job, unslopped, verified, with no leftover tools. And Can's Shepherd orchestrates coding agents in Herdr, an open runtime. Both lean on tight scope, and that pairs nicely with the new Main Bot as a coordinator.
James Turner
So here's what I'd do this week. One, update to at least 0.59.0 and star a Main Bot. Two, if you run a Team Bot, add a Manager. Three, keep drafts on for anything customer facing. And four, bookmark the official changelog. That's the episode, and I'll see you next time.