A Grok Bot is an always-on AI teammate in xAI's Grok Bot product. Each Bot has its own computer, signs in to the tools you already use, works through a job from start to finish and checks in with you when something needs your approval. A shared Grok Bot is one whose creator has published its setup as a public x.ai/bot link, so anyone can add a copy to their own account.
What a Grok Bot does
A Bot is built around a job rather than a single prompt: triaging an inbox, researching accounts, reviewing pull requests or writing a weekly briefing. It keeps working context between runs, uses the tools you connect and can run on a schedule.
Good Bots are explicit about where they stop. Many draft work for you to approve instead of sending, publishing or spending on their own.
Shared Bots and x.ai share links
When a creator shares a Bot publicly, it gets a page at x.ai/bot/… with an "Add to Grok Bot" button. Adding it copies the Bot's public configuration — its instructions, skills and routines — into your own account.
It does not give you the creator's logins, computer or conversation history, and it does not give the creator access to yours. You connect your own tools after adding it.
Bots, Blueprints, skills and routines compared
| Term | What it is | Where it lives |
|---|---|---|
| Shared Bot | A complete, working Bot its creator published as a public x.ai/bot link | x.ai; listed on GrokShelf as a Public Bot |
| Blueprint | A reusable setup written by GrokShelf that you adapt into your own Bot | GrokShelf; not a verified public Bot |
| Skill | Reusable instructions a Bot follows for one repeatable piece of work | Inside a Bot's configuration |
| Routine | A workflow assigned to a Bot to run repeatedly, often on a schedule | Inside a Bot's configuration |
| Team Bot | A Bot shared inside an organization rather than publicly | Your team's Grok Bot workspace |
How to add a shared Grok Bot
- Open the Bot's page on GrokShelf and read what it does and where it stops to ask you.
- Select "Open in Grok" to go to its x.ai share page.
- Select "Add to Grok Bot". A copy of its configuration is added to your account.
- Connect only the tools it needs for its job.
- Run it once on a low-stakes task and check the result before relying on it.
How GrokShelf verifies public Bots
Every listing marked Public Bot links to a canonical x.ai/bot share page. GrokShelf checks that the page exists, shows the "Add to Grok Bot" action and names the Bot and its creator, then re-checks it on a schedule. Each Bot page shows the date of its latest check.
A check is not a review. The Public Bot badge means the share page was real when we last looked. It does not mean the Bot is good at the job, safe with your accounts, or written up by us. Listings with a stated audience and example tasks are the ones we describe in full. Other verified Bots stay searchable in Explore without being treated as finished guides.
Where a Grok Bot actually runs
The desktop app runs on a Mac (Apple silicon or Intel), Windows (x64 or Arm), and Linux (x64 or Arm). Phones use the iPhone app on iOS 18 or later, or the Android app on Android 9 or later. Installers are on the Grok Bot download page and at x.ai/bot. There is no separate Grok Bot account: the desktop app signs in with the Cursor account that holds your plan, or with a Grok account when access comes from a Grok Business seat (get started).
The work itself happens on a cloud computer the Bots share, not on the laptop you close. From the phone you can message a Bot, watch that computer, approve an action, and pause a routine. Teaching a workflow by demonstrating it, testing a routine, and updating the computer stay on the desktop app. Prices, the trial, and which plans include it are in how much Grok Bot costs.
What a Grok Bot does, and what it refuses to do
A useful Bot is hired for one job. The first message states the outcome, the sources that matter, the constraints, and where it must stop. xAI's own setup example is a product-performance Bot that preserves links, separates evidence from guesses, and never changes production settings (get started). That shape shows up across the catalog: a research Bot cites sources, an inbox Bot drafts instead of sending, a coding Bot reviews a pull request instead of merging it.
Work starts in three ways. You type or talk. A routine runs on a schedule, such as a weekday morning. Or an event arrives from Slack, GitHub, Linear, Sentry, PagerDuty, email, or a webhook. Each Bot can hold up to 50 routines, and a skill you save is available to the other Bots on the account (skills and routines).
It does not replace the chat box on x.com, and it is not a single prompt you paste once. It also does not spend, send, delete, or change production systems unless you have allowed that. xAI's guidance is to require approval for those actions. Our safety guide is the short version of the same rule.
Shared Bot, Team Bot, template, and prompt
People say "Grok template" and "Grokbot template" for a setup they can reuse. In the product, that setup is a shared Bot: a public x.ai/bot page with Add to Grok Bot. Adding it copies the public instructions, skills, and routines. It does not copy logins, the creator's computer, or old chats. You connect your own tools after that. The longer explanation, including what a marketplace search is really asking for, is on Grok templates.
A Team Bot is the private version of the same idea. One person configures it and the team uses it. It does not get a public share link. A Blueprint on GrokShelf is different again: we wrote the setup, it is not a verified public Bot, and the badge says so. A prompt is one instruction. A skill is a reusable instruction inside a Bot. A routine is that Bot doing the job again on a schedule or an event.
Grok Bot is also not Meta's Muse or OpenAI's dots. Those are one personal agent. Grok Bot is built as several Bots with separate jobs, which is why a directory of shared setups exists at all. The comparison is in Grok Bot vs Muse and Grok Bot vs dots vs Claude Duet.
How to choose one
Start from the hour you lose every week, not from a long list of capabilities. A personal assistant is several jobs: inbox, calendar, follow-ups, and protecting your time. The personal assistant roundup splits them on purpose. Coding, research, and weekly operating work are split the same way in the best Grok Bots for those jobs.
Read the x.ai page before you add anything. Check the job, the tools it wants, and whether it drafts or acts. Connect only those tools. Run one low-stakes task. If the first week of a routine is wrong, change the instructions before you add a second Bot. Fewer Bots with a narrow job are easier to trust than a sidebar full of them.
Where to start
Browse verified Bots by the job you need done, or start with a roundup like the best Grok Bots for a personal assistant. Before adding any Bot, read Using a Grok Bot safely.
Plan prices, the trial and the Windows or Mac download are in how much Grok Bot costs. How it differs from Meta's Muse is in Grok Bot vs Muse.
Before adding any of these, read Using a Grok Bot safely.