Grok Automation, Tasks, and Extensions

Grok automation, grok tasks, grok automation extension, grok extension, and grok chrome extension get mixed together because the words overlap. Inside the product, a task is something Grok runs on a schedule or on a trigger you set on grok.com. An extension is a browser add-on. xAI’s supported way to reach other software is a connector, which uses an OAuth-style consent screen. A random extension that wants your cookies is not that.

Tasks

A task is a saved instruction plus a time. People use them for a morning brief, a reminder to check a public page, or a repeated rewrite. Open the tasks or automations area in the official app, write the instruction the way you would write a chat, and set the schedule. The run spends the same plan allowance as a manual chat. A task that fires every hour on a free account will hit the cap and then skip or queue. SuperGrok raises that ceiling. It does not make the task free of the meter.

Auto Grok, as a vague search, is this feature. It is not a self-driving account and it should not hold passwords. If a task needs data from another app, connect that app in the connector screen and limit the scope. Read the first few runs yourself. A scheduled model will repeat a bad assumption every morning until you edit the instruction.

Browser extensions

Search results for a Grok AI extension include unofficial add-ons. Some wrap the public site in a sidebar. Some ask for permission to read every page you visit. Some claim to remove limits or to unlock adult settings without the official control. Those claims are the pitch. The permission list is the product. If the extension can read all sites, it can read your bank and your mail. Prefer the official site pinned in the browser. If xAI ships an extension, it will be named from their accounts, and the download guide is where that would be called official. Until then, assume a store listing is a third party.

What to automate instead

• A daily question you already paste by hand, rewritten as one task with a source link in the instruction.
• A repo check, which belongs in Grok Build or CI, not in a browser extension.
• A connector for a tool you already pay for, with the smallest scope.

Skip automations whose only job is to evade a quota or a content rule. They break when the site changes, and they put the account at risk. The official meter and the official content setting are the durable versions of those ideas.

Write a task you can audit

A task instruction should say the input, the output shape, and what to do when the source is down. “Summarize the top item on this public status page in four sentences. If the page fails, say that it failed and stop.” That run is easy to skim. “Keep me posted” is not. For the first week, schedule it once a day and read every result. Then decide if it deserves a morning slot. Each run spends allowance. An hourly task on a free account is a machine for hitting the cap.

Connectors belong in the task only after you have used them once by hand. Authorize, ask a single question, revoke if the scope was wider than the question. Browser extensions do not belong in this loop. They sit outside xAI’s consent screen and they update on a store’s schedule, not grok.com’s. If your company already blocks unknown extensions, that policy is doing you a favor. The official clients are the site and the store apps in the download guide.

Do not automate login. A task that stores a password, a cookie, or a one-time code is a leak with a schedule. Sign in yourself on grok.com. Let the task use the session you already trust, inside the product, not a script that replays your credentials. The same rule bars “unlimited” automations. They are quota evasion. They break, and they are a common wrapper for malware.

When a task needs code rather than a paragraph, move it to Grok Build or to an ordinary CI job. The chat scheduler is the wrong place to merge a pull request. It is the right place to remind you that a public changelog moved.

Put the task’s source URL in the instruction so a future you can see what “the page” meant. Public docs, status pages, and your own files are fair game. A logged-in dashboard behind someone else’s password is not. If the task starts failing after a redesign of that page, fix the instruction. Do not add an extension that screen-scrapes every site you visit in order to rescue one schedule. The failure is local. The extension would be global. Once a week, delete tasks you no longer read. A graveyard of schedules is how a free allowance disappears before breakfast on a plan you forgot you were using. Name each task after the outcome, not after “test.” You will not remember what test 4 was supposed to watch. Pause a task while you are on holiday so it does not spend the allowance on an empty week.