Grok Build 1.0.49: Hook confirmations now cover all modes, while web search and

Release notes

FEATURE

Hook confirmations now cover all modes, while web search and image generation check prompt policy first

When you have Grok handle tasks, the rules for when it pauses to ask for your authorization are now clearer.

When performing operations such as web searches, web scraping, and image generation, Grok now follows your prompt_policy settings and existing rule evaluations before popping up a prompt to ask you. For hooks (scripts triggered when specific events occur), permission prompts now appear reliably under every approval mode, ensuring that automated scripts prompt for confirmation properly across all environments.

FEATURE

One-time approvals apply only to the next command, while process termination blocks accidental kills of shell wrappers

When you approve commands on the prompt screen, the scope governed by each approval is now defined more precisely.

Now, when you select 'Allow once' on a permission card, this release strictly applies only to the next shell command, and subsequent commands are not passed along with it. When running commands like pkill -f and pgrep -f to search for or terminate processes, if the specified matching pattern would kill the shell wrapper enclosing Grok itself, execution is now rejected early to prevent accidental terminal disruptions.

Original changelog

Original changelogHook confirmations now cover all modes, while web search and image generation check prompt policy first

Hook permission prompts appear in every approval mode
Web searches, fetches, and image generation follow the `prompt_policy` setting and rule decisions before they prompt

Original changelogOne-time approvals apply only to the next command, while process termination blocks accidental kills of shell wrappers

Allow once on a permission card applies only to the next shell command
`pkill -f` and `pgrep -f` are rejected earlier when the pattern would kill their own shell wrapper