Super Intelligence One
Personal Intelligence · 20 November 2026 · 5 min read

Grok Bot Updates 09: tool permissions and routine reconnect cards

One official changelog entry since Update 08 lets you set each connector tool to Always allow, Auto-review, Needs approval or Blocked, makes routines better at telling you when a sign-in has dropped out, and fixes a long list of small annoyances. The Mac app on Homebrew is now 1.2.3.

The official Grok Bot changelog at x.ai/changelog/bot has one new entry since Updates 08, which covered version 1.2.0 of 16 November 2026:

  • 18 November 2026: version 1.2.3, "Tool permissions and routine reconnect cards" (also includes 1.2.1 and 1.2.2)

As at 20 November 2026 (Melbourne time), the Homebrew cask for the Mac app shows version 1.2.3.

This post is based only on that official entry. We have not tested these features ourselves. Grok Bot features often roll out gradually, so what you see may differ by plan, account and app version. Some items below are marked in the changelog as needing a minimum app version, or as applying only to Teams or Enterprise, and we say so where that applies. Treat this as a guide to what is being announced, not a promise of what is on your screen today.

Set the rules for each tool

The headline item is on connector pages. You can set each tool a connector offers to one of four settings: Always allow, Auto-review, Needs approval or Blocked. The changelog says this needs Grok Bot 0.70.2 or later.

Everyday example: say you connect your email. You might let the Bot read and search without asking, keep sending on Needs approval, and block deleting altogether. You decide tool by tool, rather than trusting or distrusting the whole connection.

Also in the "New" list:

  • Clicking a message button in an MCP App puts its text in the chat box, ready for you to send. You still press send yourself.
  • Signing up for Grok Bot requires you to be 18 or older.
  • Team admins can limit which tools the built-in GitHub connector offers, and the Bot says when a team admin has limited a tool (tagged Teams).

Routines that tell you when they need you

Several improvements are about routines, the jobs the Bot runs on a schedule:

  • When a routine needs you to reconnect an account, its reconnect card also arrives as a notification and as a Slack or Microsoft Teams direct message. The changelog says this needs Grok Bot 0.79.2 or later.
  • A routine that loses a connector sign-in skips its scheduled runs until you sign back in.
  • Routines can read the earlier conversation in the chat they run in.
  • When a connector one of the Bot's helpers uses is signed out, a reconnect card appears in your chat (also 0.79.2 or later).

Everyday example: a weekly routine that checks your calendar for clashes stops working because the calendar sign-in expired. Under these notes, the routine skips its scheduled runs until you sign back in, and the reconnect card can reach you as a notification or a direct message. The practical lesson is to answer reconnect cards promptly, because a skipped run means that job did not happen that week.

Smarter choices and memory

  • For a site that has a connector, the Bot uses the connector, or shows its connect card, before opening the browser.
  • The Bot keeps separate memories for people and organisations, your profile, your standing instructions, and your projects.
  • Asking for an X post when X isn't connected shows the X connect card (needs Grok Bot 1.1.0 or later).
  • With a saved card and no top-up rule, Buy credits opens with automatic top-up turned on (needs Grok Bot 1.1.0 or later). Check that setting before you confirm anything. The notes give no amounts.
  • Each turn keeps its own MCP App card, so a later card no longer replaces an earlier one.
  • When booking flights, the Bot follows each airline's own booking steps, and sends you the link instead of clicking again when a final purchase can't be confirmed.

Fixes

The "Fixed" list is long. In plain terms:

  • The usage limit tray goes away after you add credits, and after you change plans the usage limit warning clears once the new plan takes effect.
  • When a connector you already connected is missing its tools, the Bot reloads them and continues in the same reply.
  • Pressing Send again on a draft card while the first send is still running no longer leaves the card stuck on "Sending".
  • Photos and PDFs you send from the phone reach your Bot's computer, so it can open them.
  • Macs show their computer name instead of their network host name on permission cards and in the computer list.
  • Product searches try again once when the search service briefly fails.
  • Published Pages no longer stall, jump, or lose their scroll position when you print them.
  • Personal MCP servers saved in the app follow your team's MCP allowlist and the 100-server limit.
  • While a call transfer is still ringing, the Bot no longer says the transfer failed.
  • On a Bot's own Slack app, a former owner is no longer treated as the owner and is asked to link their account.
  • When a Bot's owner has no seat on the Bot's team, the Bot says so once instead of retrying (tagged Teams).

Plan and admin items

Several entries are tagged for Teams or Enterprise in the changelog. In Slack and X Chat, asking for a connector your team admin blocked gets a reply that it is blocked and why (Teams). When a team rule blocks one of the Bot's tools, the Bot says a team admin can change it in the team's MCP settings (Teams). The built-in GitHub connector follows your team's MCP allowlist, so it is off unless a rule allows it (Teams). Team admin MCP rules also stop plugins your identity provider manages, and the connector list marks them as Blocked by team admin (Enterprise). Team data retention also deletes meeting transcripts and notes older than the team's limit (Teams). If you are on a personal plan, you can ignore those. If you are on a team plan, ask whoever administers it.

How to get started

  1. Update the app (Homebrew users: `brew upgrade --cask grok-bot`) and check that you are on 1.2.3.
  2. Open a connector page you already use and look at the per-tool settings (if you are on 0.70.2 or later). Start cautious: keep anything that sends, posts, pays or deletes on Needs approval or Blocked.
  3. If you run routines, watch for reconnect cards and sign back in quickly so scheduled runs are not skipped.
  4. Don't expect every item to be live on your account yet. If something is missing, check again after the next update.

Where SI1 fits

At Super Intelligence One, we help business owners and everyday users put AI to practical use, without the hype. Per-tool permissions are a good example of a simple rule: let the assistant do the legwork, but decide in advance which actions need a person to say yes. If you want help setting up an assistant with sensible permissions, get in touch.

Sources

  • Official Grok Bot changelog at x.ai/changelog/bot, checked 20 November 2026 (Melbourne time): 18 November v1.2.3 "Tool permissions and routine reconnect cards" (also includes 1.2.1 and 1.2.2)
  • Homebrew cask grok-bot: current version 1.2.3
Next step · 45 minutes, no charge

Start with one conversation about where AI fits in your business.

We'll look at how you work now, where the time goes, and which opportunities are worth pursuing first. You leave with a short written summary either way.