Grok Bot in October: fewer approvals, payments and new admin controls

Grok Bot shipped 14 releases between September 28 and October 26, 2026, according to its public changelog. We last covered it when Team Bots launched. The month since then points in one direction: bots that act with fewer interruptions, can pay for things, and have their own email addresses. Team admins get more controls to rein them in.

This is a summary of the changes that matter to a business, based on the changelog's own wording. We have not tested these features, and the changelog does not always say which plans include them.

Fewer approval cards, and more actions that go straight through

Grok Bot decides when to ask permission with a system it calls Auto-review. Several October releases loosen it deliberately:

• v0.75.5 (October 23): "Emails and Slack messages you ask a Bot to send go out once Auto-review allows them." Sends from routines and other turns still wait as drafts. Auto-review also "asks less often for an action you asked for in your own words."
• v0.75.8 (October 24): Auto-review "takes a second look before showing an approval card, so fewer safe actions need one."
• v0.77.0 (October 26): Auto-review "lets through more private actions you can undo without an approval card," and background work you start in your own words no longer needs approval to begin. Approval cards stay open for 30 minutes instead of 10.

The same releases add guardrails. Before an action it cannot undo, such as sending, posting, buying or deleting, a bot checks your own messages for approval (v0.70.2). After you deny a card, it stops and does not retry that action until you send another message (v0.75.5). Auto-review "no longer waves through an action your request said to stop before," such as sending a message you asked only to draft (v0.75.5). The rules are now visible in one place: v0.77.0 adds a Permissions section in Settings that lists rules under Always Ask and Allow without Asking.

What to check: what your own requests now authorize. If staff phrase requests as "send the follow-up to the client," that phrasing may now be enough for an email to go out without a draft card. Review the Allow rules each person has accumulated, and decide which actions should stay under Always Ask for everyone.

Bots can now pay, sign in and send from their own address

October added the pieces an agent needs to transact on its own:

The 1Password change is the most careful design in the list: the changelog says 1Password fills the login in the bot's browser "without the Bot seeing it." The Vault works the other way. Bots fill saved logins and cards themselves, and as of v0.77.0, they "try your saved Vault logins and cards before a password manager." For a business, that is a choice between two storage models, and the default now favors the Vault.

Bot email identities also grew up quickly. Bots can claim an address and receive mail (v0.70.2), send from tagged addresses such as name+shop@ (v0.71.2), forward mail with attachments (v0.75.5), and include a one-click unsubscribe on every email sent to one person (v0.77.0). They also stop emailing addresses that have permanently bounced. If you allow bots to email customers or suppliers, treat that address as a sending domain you are accountable for.

More controls for team admins

Team Bots launched as a public beta on Teams and Enterprise plans. The following month added most of the controls an administrator would ask for:

• Who manages a bot: a Team Bot's creator can add Managers who can change its skills, plugins, secrets and Slack app (v0.64.0).
• Who can use it: people not on a Team Bot's share list, including teammates, lose access until an owner shares it (v0.75.8). Admins can limit sharing to admins only (v0.77.0) and control whether members publish bot templates publicly, to the team, or not at all (v0.77.0).
• Bot-to-bot work: admins can turn off messaging between bots, so members' bots cannot hand work to each other (v0.71.2).
• Enterprise data: admins can recreate, terminate or delete members' bot computers (v0.71.2) and permanently delete a member's Grok Bot data, including through the Admin API (v0.75.2). Audit logs now record changes to a team's trusted certificate authorities (v0.77.0).

Slack got safer, and one fix is worth noticing

Slack is where shared bots meet people who may not have the same access. Bots now record who requested each message they post (v0.75.5) and check each post against who can read the conversation before sending (v0.77.0).

The v0.77.0 Fixed section also says: "In Slack, people without a linked Grok Bot account can't use the owner's logins or private data through the owner's Bot." The changelog does not say whether this was previously possible in practice or for how long. If your team used personal bots in shared Slack channels before October 26, it is reasonable to ask your account contact about the scope of that fix.

One more data-handling change is useful: after a bank or brokerage connector returns data, a bot now asks before sharing it anywhere else (v0.70.2).

What this means if you are evaluating Grok Bot

The pace is the first takeaway. Fourteen releases in four weeks means the product you evaluate in a trial will differ from the one you run a month later. Several of those changes alter default behavior rather than add options. Reread the changelog before relying on an earlier test result.

The second is that the controls live inside the vendor's product. Auto-review, the Vault and team sharing rules are all configured in Grok Bot and enforced by Grok Bot. That is normal for a hosted agent, and the October releases make those controls more visible and more granular. It is still a different model from running agents under a policy you hold yourself, as tools such as NVIDIA OpenShell do: there, the agent cannot change its own permissions, and the policy file is yours.

For a trial, we would check four things:

1. Which actions go out without a card when staff phrase requests naturally.
2. Whether saved payment methods and logins live in the Vault or a password manager, and who can see them.
3. Who is on each Team Bot's share and manager lists, and whether bot-to-bot messaging should be on.
4. What a person in a shared Slack channel can get a bot to do for them.

We will keep tracking the Grok Bot changelog alongside OpenAI's dots and Meta's Muse, and will update our agent comparison when the differences change.