← All updates

Grok Bot · Published: · ACT

Type: General Agent

Grok Bot's latest changelog details per-tool permission controls

Your move: Review each connected tool, rather than treating an app connection as blanket consent.

Grok Bot's November 18 changelog documents four choices for each tool on a connector page: Always allow, Auto-review, Needs approval and Blocked. It also says routines skip scheduled runs after losing a connector sign-in, until you reconnect. Reconnect cards can arrive through notifications and Slack or Microsoft Teams direct messages.

Why it matters

Review tools that send, delete or change data separately from those that only read. Use explicit approval or blocking where automatic review is not enough. The catch: These are bundled 1.2.1-1.2.3 notes, not proof every control first shipped November 18. The tool controls are marked 0.70.2+; notification and helper reconnect cards require 0.79.2+. The notes do not state the initial per-tool default. General Auto Review is on by default, but it is model-based: many actions run without a fresh human approval. Turning it off also stops using personal Custom Rules. These controls are not proof that background-access or training-data concerns are fixed. We have not tested their enforcement. Sources: November 18 changelog · Approval settings and limits

Source: Official November 18 changelog ↗

Published by Agent Log. The summary reports the linked source; “Why it matters” and the verdict are Agent Log's interpretation.

More Grok Bot updates →