Skip to content
THE INDEPENDENT GROK BOT REGISTRYPublic links · saved shortlists · creator review queue
Grok Bot Templates
EngineeringOn demand

Browse

One bot owns the browser and the rest of your team can use it, so pages, sessions, and logins stay in one place instead of being rebuilt per task. Its interface is aimed at awkward s…

One bot owns the browser and the rest of your team can use it, so pages, sessions, and logins stay in one place instead of being rebuilt per task. Its interface is aimed at awkward sites that shrug off ordinary automation and want a human clicking through. Treat it as plumbing for the rest of your fleet.

Share link verified 4 Oct 2026 by its source registry.Always review tools and permissions inside Grok before connecting them.

General guidance for engineering bots

Review codebase, shell, browser, and deployment access before use. Start with read-only permissions wherever the job allows it.

What a template shares

Adding a template creates an independent copy of the Bot on your account. A template can bundle instructions, selected memories, skills, routines, and first-party integrations — it never carries the creator's conversation history, signed-in sessions, API keys, or custom MCP servers.

How adding a template works
WHAT “LINK CHECKED” MEANS

We confirmed that the URL uses the official x.ai domain, has a valid public-template shape, and returned successfully on the date shown. We have not certified every instruction, connected tool, or future edit. Review the live configuration before granting access.