The changes
Oct 23 · v0.75.5
A Vault for logins, cards and contact details
- What changed
- Bots can save your logins, cards and contact info to a Vault in Settings, and fill them in to sign in or check out. It needs Grok Bot 0.75.2 or later.
- Why it matters
- It’s a safer place for private details than a chat message, and it means fewer “please type your password” interruptions.
- What to do
- Update the app, then move any login you’ve been handing your bot into the Vault. Keep purchases behind approval.
Source: Grok Bot changelog, v0.75.5
Oct 23 · v0.75.5
Fewer approval cards for things you asked for
- What changed
- Auto-review asks less often when you asked for the action in your own words. If you deny an approval card, the bot stops and won’t try that action again until you send another message. Emails and Slack messages you ask a bot to send go out once Auto-review allows them, while sends from routines still wait as drafts.
- Why it matters
- Fewer interruptions for clear requests, and routines still can’t send without you.
- What to do
- Be explicit in your own words when you want something sent. Keep “draft only” in routine briefs; it’s still respected.
Source: Grok Bot changelog, v0.75.5
Oct 23 · v0.75.5
Routines can run more often
- What changed
- All your routines together can run up to 300 times an hour instead of 100, and each routine up to 200 times.
- Why it matters
- Monitors and event-driven routines are less likely to hit a ceiling.
- What to do
- Nothing required. If you raise frequency, make sure each run is cheap and only reports when something changes.
Source: Grok Bot changelog, v0.75.5
Oct 22 · v0.75.2
Pages: reports and dashboards you edit together
- What changed
- Bots can build Pages, such as reports, memos and dashboards, that you edit together or have the bot keep up to date. You can pin Pages, files and links to a Pinned section in the Library.
- Why it matters
- A daily brief or project tracker can live in one place that updates, instead of a new chat message every time.
- What to do
- Ask your chief of staff or brief bot to keep its report as a Page, and pin it.
Source: Grok Bot changelog, v0.75.2
Oct 22 and Oct 7 · v0.75.2, v0.68.1
Video creation and slide decks
- What changed
- Bots can create videos from a description or an image you share. Earlier in the month, bots gained slide decks: they show sample slides to choose from and deliver PowerPoint or Google Slides files.
- Why it matters
- Content and reporting bots can produce finished formats, not just text.
- What to do
- If you have a content lane, add “deliver as slides” or “make a short video draft” to its skills, and keep publishing approve-first.
Oct 11, Oct 14 and Oct 22 · v0.70.2, v0.71.2, v0.75.2
Bots have their own email inboxes
- What changed
- Bots can claim their own email address and receive mail there; mail they send from it waits for your approval on a draft card. They can use tagged addresses like name+shop@, and a routine on a tag runs only for that mail. Routines can now read the bot’s inboxes.
- Why it matters
- You can give a bot its own address for sign-ups, receipts or forms, and trigger work from incoming mail without exposing your personal inbox.
- What to do
- Use a tagged address per purpose (for example +receipts) and point a narrow routine at it.
Oct 14 · v0.71.2
Room for many more plugin skills
- What changed
- Bots can use up to 200 skills from your installed plugins instead of 24.
- Why it matters
- Plugin skills you add are no longer silently left out.
- What to do
- Good moment for a skills check-up: more skills loaded means overlaps matter more. See our Bot Doctor template.
Source: Grok Bot changelog, v0.71.2
Oct 14 · v0.71.2
Low-disk warnings that ask before deleting
- What changed
- When a bot’s computer runs low on disk, the bot tells you once, names the biggest files, and deletes them only if you agree.
- Why it matters
- Fewer mystery failures from a full disk, and nothing disappears without your yes.
- What to do
- Keep backups outside the bot’s computer so clean-ups are never risky.
Source: Grok Bot changelog, v0.71.2
Oct 11 · v0.70.2
Bots check before actions they can’t undo
- What changed
- Before an action it can’t undo, such as sending, posting, buying or deleting, a bot checks your own messages for approval.
- Why it matters
- This is the same approve-first habit we teach, now built in.
- What to do
- Write your approvals plainly in your own messages (“yes, send it”). Vague replies are harder to read as approval.
Source: Grok Bot changelog, v0.70.2
Oct 11 and Oct 2 · v0.70.2
Templates are easier to find
- What changed
- Bots can find a bot template that fits what you describe and link it in the chat. Marketplace is now called Connect Apps, with bot templates on the web.
- Why it matters
- More templates in front of more people, so checking them before you install matters more.
- What to do
- Read our guide to installing templates safely before adding one.
Source: Grok Bot changelog, v0.70.2
Oct 2 · Oct 2 release
Your primary bot offers to help
- What changed
- Your primary bot, marked with a star, will spot work it can take off your plate and offer to handle it. Needs Grok Bot 0.59.0 or later.
- Why it matters
- It’s a natural fit for a chief of staff role.
- What to do
- Make your coordinating bot the primary bot, and give it your lanes so its offers route to the right bot.
Oct 14 · v0.71.2
For teams: admins can turn off bot-to-bot messaging
- What changed
- Team admins can turn off Messaging between Bots under Bot capabilities on the dashboard, so members’ bots can’t message or hand work to other bots.
- Why it matters
- If your swarm relies on handoffs and you’re on a team plan, this setting can quietly break it.
- What to do
- Team users: if handoffs stop working, ask your admin whether Messaging between Bots is on.
Source: Grok Bot changelog, v0.71.2
This is our plain-language reading of the official changelog. Some features roll out gradually or need a recent app version. Swarm School is independent and not affiliated with Grok Bot’s makers.