Grok Bot glossary: Bots, skills, routines, Auto Review and more
Grok Bot has its own vocabulary. This glossary defines the terms you will see on Bot profiles and in the docs, from primary Bot and memory to skill, routine, Auto Review, Vault, template and Team Bot, in one or two plain sentences each, with the official name where it differs from community slang.
- Bot
- An AI teammate with a name, a job description, its own memory and access to your shared cloud computer and connected apps.
- Primary Bot
- Your main point of contact. It checks in on its own and can coordinate your other Bots. A Team Bot cannot be your primary Bot.
- Memory
- Preferences, standing rules and a dated work log a Bot carries between chats. Your name and time zone are shared by all your Bots.
- Skill
- A saved, reusable set of instructions for a task: inputs, steps, checks, output and what needs approval. Private skills are shared across your Bots.
- Teach a task
- Recording a browser workflow (up to ten minutes) so the Bot drafts a skill from your demonstration. Rolling out gradually.
- Routine
- An instruction for one Bot to run a workflow on a schedule or when an event happens, such as a Slack message, email or webhook.
- Trigger
- The event that starts a routine: Slack, email to the Bot, GitHub, Linear, Sentry, PagerDuty or a webhook call.
- Connector (connected app)
- An app such as Gmail, Slack or Notion that a Bot can work in directly. Called Connect apps in the sidebar.
- MCP server
- The standard way AI tools connect to a service. Bots can use custom MCP servers for services without a built-in connector.
- Cloud computer
- One persistent machine with a browser, files and terminal shared by all your Bots. Each Bot gets its own screen.
- Auto Review
- The built-in check that reviews commands and actions before they run and asks you about risky ones. On by default.
- Ask first rule
- A custom rule (Settings, General, Bot, Custom Rules) that makes a matching action, like sending an email, always wait for your approval.
- Approval card
- The prompt a Bot shows when an action needs your OK. Cards from unattended work expire after about 30 minutes.
- Vault
- Where your saved logins, cards and contact details live. Bots fill them into pages without seeing the values.
- Secure Form
- A form the Bot sends you to enter a login or card for a site, filled directly into the page.
- Template
- A shareable Bot recipe: identity, description, skills and routines, without the author's data, logins or chats.
- Marketplace
- The x.ai gallery of Bot templates from the Grok Bot team and the community.
- Team Bot
- One Bot shared with your team, with private chats per person. Available on Team and Enterprise plans.
- Cloud Agent
- A Cursor coding agent that a Bot can launch to write code and open a pull request.
- Handoff
- One Bot passing its result to another Bot instead of to you.
- Hub Bot
- Community term for a Bot that collects specialists' results and is the only one that messages you.
- Anti-job
- Community term for something a Bot is explicitly told never to do.
- No-op
- A run where nothing changed. Well-built Bots stay silent on no-ops.
- The usage allowance on The X Subscription shared by Grok Bot, Grok and Cursor for one seat.
Turn this into a working Bot. The free AllGrokBot Bot Builder writes the instructions, routines and approval rules for you in about two minutes.
FAQ
What is an anti-job?
Something a Bot is explicitly told never to do, such as posting, sending or paying. It is a community term for a pattern many official templates use.
What is the difference between Auto Review and Ask first?
Auto Review is the built-in check on every action. Ask first is a custom rule you add so a matching action always waits for your approval.
Related Grok Bot news
Keep learning
- How Grok Bot works: computer, memory, skills, approvals and Team Bots
- Grok Bot getting started guide: what it is and your first Bot
- Grok Bot FAQ: plans, safety, memory, models and more