Permissions explained

Chrome surfaces scary-sounding capabilities because they are powerful. Grok Automate requests the smallest set we have found that still keeps Imagine automation reliable on modern Grok builds.

debugger

Grok's composer relies on editors that ignore synthetic typing events. We attach Chrome DevTools Protocol briefly on grok.com tabs so keystrokes register as trusted input — this triggers Chrome's started debugging banner while a queue item runs.

tabs + scripting

We locate your Imagine tab, reload safely between queue items when needed, and clear stale Grok client storage so prompts don't bleed across runs.

downloads

Saves generated assets straight into your Downloads hierarchy using filenames derived from prompts.

storage

Keeps queues, counters, and settings locally; optional Pro caching mirrors policy described on our Privacy page.

https://grok.com/*

Host permission limits injection and automation strictly to Grok's origin — not arbitrary websites across the web.

Need more detail?

Read the full privacy policy or Chrome Web Store programme policies if you're comparing extensions before install.