Grok Bot went from an early beta to a product with team features, enterprise controls and a release every few days. If you looked at it in August and moved on, a lot has changed. This guide sorts the releases into what affects a small business and what you can safely ignore for now.

Where it started in August

Grok Bot launched on 11 August 2026 as a beta for desktop and iOS. The idea was simple to explain: a Bot is an AI teammate with its own computer in the cloud, it signs into the tools you already use and comes back when something needs your approval (xAI, Introducing Grok Bot).

The launch post describes Bots that remember conversations and can follow along while you do a job once, then save that workflow as a routine. It also describes several Bots working in parallel, with one managing the others (xAI, Introducing Grok Bot). We covered that coordination pattern earlier in one coordinator for many AI agents, so this article stays with what is new since then.

More plans include it

On 26 August, access widened. Grok Bot is now included with SuperGrok, SuperGrok Plus and SuperGrok Heavy, Cursor Pro, Pro+ and Ultra, and the Cursor Teams plans. xAI says Grok Bot has its own usage, separate from your Grok and Cursor plans, so work you hand to a Bot doesn't eat into your existing allowance (xAI, Grok Bot is now included with more plans).

For a small business this matters more than any single feature. If someone on the team already pays for one of those plans, trying a Bot costs nothing extra. The documentation adds that usage resets weekly (Grok Bot overview), which makes it easier to see whether a recurring job fits inside the allowance before you build on it.

The same post lists jobs people were already giving to Bots, including an office manager that books jobs across Gmail, Slack and a client portal, and an inbox manager that leaves only the messages that need a person (xAI, Grok Bot is now included with more plans). Treat those as examples of the shape of work, since the vendor wrote them.

X became a working tool

On 29 August, xAI announced a tighter X integration. You connect your X account in Grok Bot, and xAI creates a developer account for you if you don't have one. Paid users get free X API credits to start, and a Bot can then search posts, read your timeline and check mentions (xAI, Grok Bot now works with X).

You can also start work by tagging @bot in a post or reply. Your main Bot picks up the post as a task, while @bot confirms with a short public reply. The documentation notes this needs a connected X account and isn't available in every region yet (Grok Bot overview). Before you use it for anything client related, remember the confirmation reply is public.

Enterprise controls arrived

On 3 September, Grok Bot became available for enterprises with access, network and audit controls. The announcement states that each user's work runs in its own isolated environment and that a Bot has no access by default; it reaches only the accounts you sign it into (xAI, Grok Bot for Enterprise).

Most small businesses won't buy an enterprise plan, but the controls tell you how the product thinks about risk. The security documentation describes Auto Review as a model-based check that complements least privilege and explicit approval boundaries (Grok Bot approvals, security and privacy). That framing is useful at any size: an automated check helps, and you still decide what a Bot may touch.

Team Bots: one Bot, shared by a team

The biggest change for teams came on 28 September. A Team Bot is built around a shared role or workflow, and everyone on the team can work with it. It brings together context such as files and instructions, plugins for apps like Notion or GitHub, credentials for services without a plugin, and memories of what it learns (xAI, Team Bots).

Two details matter for small teams. Each person's conversations with a Team Bot stay private, because the Bot keeps separate context and memories per user while sharing the skills. And a Team Bot can join Slack with its own handle, so a channel can ask it questions in one place (xAI, Team Bots).

Later releases filled in the practical parts. Since version 0.64.0, the creator of a published Team Bot can add managers who change its profile, skills, plugins and secrets. Version 0.65.0 added voice chat with a Team Bot (Grok Bot changelog).

Think of a Team Bot as the shared office binder that can also do the work. If your business runs on one person knowing how the quote template works, a Team Bot is a way to make that knowledge available to the next person.

Approvals got clearer

Several releases in late September and early October changed how approvals look and behave, according to the Grok Bot changelog:

  • In Slack threads, a Bot that needs your approval now posts a review card only you can answer, instead of dropping the action (0.63.0).
  • Approval cards show when an "Ask first" rule paused an action, with a link to edit the rule (0.67.0).
  • Approval cards now name the Bot and quote its instruction, and saved rules are called Custom Rules in Settings (0.68.0).

One change deserves caution. Since 0.64.0, email and Slack draft cards offer "Disable drafts for this Bot", so that Bot sends messages directly (Grok Bot changelog). It saves clicks. For anything a customer reads, we would keep drafts on until the Bot has shown, over a few weeks, that its messages need no correction.

The primary Bot now offers to help

Version 0.66.0 introduced proactivity: your primary Bot, marked with a star, will spot work it can take off your plate and offer to handle it (Grok Bot changelog). The word that matters is offer. It proposes, and you decide.

This is useful for owners who don't have time to think about what to delegate. It also means the Bot reads more of what you connect. Connect only the accounts you would show a new assistant in their first month.

Smaller changes that add up

The Grok Bot changelog for 0.68.0 and 0.68.1, released on 5 and 7 October, includes:

  • Bots can build slide decks with you, show sample slides to choose from and deliver PowerPoint files or Google Slides.
  • Formatted emails from a draft card, so recipients see headings, bold text and lists.
  • Email drafts can go out from a verified Gmail send-as address.
  • The Bot's computer screen grew to 1920 × 1200 from 1280 × 800, which helps when you watch it or take over.
  • Automatic updates are on by default since 0.65.0; you can turn them off in Settings.

None of these change what a Bot is. They remove friction, and friction is usually why a pilot stalls.

What this means for a small business

Grok Bot is still young. Releases arrive every few days, and the changelog is full of fixes, such as Gmail actions that failed less often after 0.68.1 (Grok Bot changelog). That pace is good news for features and a reason to re-test anything you automate after an update.

A sensible way to start:

  • Check whether someone on the team already has an eligible plan before paying for anything.
  • Give one Bot one recurring job with a clear finish line, such as a weekly overview of open quotes.
  • Keep drafts on and keep sending, paying and publishing behind your approval.
  • If more than one person needs the same Bot, try a Team Bot and decide who manages it.
  • Write down which accounts each Bot can reach and review that list every month.

Our next article shows how to turn a job you do every week into a routine, and how to test it before it runs alone: teach a Bot a task once.

If you want help choosing the first jobs and setting approval rules that fit how your business works, that is part of our ongoing tech partnership work.