Grok Bot guide

Grok Bot prompts, templates, and workflows

Grok Bot is xAI's product for persistent AI teammates that work across apps and websites on a cloud computer. This page explains the product, then connects you to public Templates and documented Use Cases for real jobs.

What is Grok Bot?

A Grok Bot is a named, durable AI teammate with its own role, conversation, and working context. It can use connected tools, a browser, files, and a terminal to complete work in the destination rather than stopping at a chat draft. Bots can keep working in the cloud, run learned workflows as routines, and coordinate with other Bots when a job needs specialists.

Bots on one account share a cloud-computer environment, so separate Bots organize ownership but are not a security boundary. Use explicit approval rules for sending, publishing, purchasing, deleting, permission changes, and production changes. Product facts here were checked against the official Grok Bot documentation on August 30, 2026.

Choose a Bot by the job

Start with one end-to-end outcome, not a catch-all helper. Add another Bot only when a durable specialist needs different tools, context, working style, approval rules, or cadence. These source-backed listings are useful starting points:

Template or documented Use Case?

An installable Template requires a creator-published https://x.ai/bot/<id> link. It opens a public preview and lets an eligible user add a copy. A public post or guide without that link proves a Use Case, not an installable Template. Grokbotlist keeps those modes separate and never invents or rehosts a configuration.

Read how Grok Bot Templates work, including what a public share exposes, what stays private, and how to evaluate a third-party Bot before adding it.

Set up the first workflow

  1. Give one Bot a specific owned outcome, approved sources, a reviewable result, and an approval boundary.

  2. Run one real task and require evidence such as links, screenshots, or an action log.

  3. Correct the process and save the reliable method as a skill.

  4. Only then add a routine that defines the trigger, time zone, stale-data policy, and failure destination.

Continue with the step-by-step creation guide, compare skills and routines, decide between an agent, assistant, or fixed automation, or design a small team of specialist Bots.

Browse all 355 source-backed Bots

Compare the job, tools, public source, and verified Template status.