Grok Bot Glossary: Bots, Skills, Routines and More
The words you will see in Grok Bot, in plain English, with a link to where each definition comes from and a tip that puts it to use.
- Bot
- An AI teammate with a name, a job and its own memory. You work with it by messaging it. Each Bot keeps its own conversations and learned context. (source)
- Primary Bot
- Your main Bot, marked with a star. It picks up tasks you start from X and can offer to take work off your plate. (source · tip: Pick a main Bot so it can see and delegate across your team)
- Description
- The text in a Bot's details that sets its job and rules. It is copied when you duplicate a Bot, while memory starts empty, so lasting rules belong here. (source · tip: Keep lasting rules in the description, not memory)
- Team Bot
- A Bot published to your Cursor team. Teammates chat with it in the app or Slack, each in their own conversation, and their use counts against their own allowance. (source · tip: Turn a Bot into a team Bot your colleagues can use)
- Group chat
- A chat with several Bots. Every Bot in it answers, so it uses more usage than a one-to-one chat. (source · tip: Use a group thread to watch Bots work together)
- Skill
- A saved, reusable set of instructions. A good one says when to use it, the inputs and access it needs, the steps, how to check the result, what to return and what needs approval. Type / to use one. Private skills are shared across your Bots. (source · tip: Do it by hand, save a skill, then schedule)
- Teach a task
- Record yourself doing a task on the Bot's computer (up to 10 minutes, no audio) and the Bot turns it into a draft skill. Rolling out gradually. (source · tip: Teach a task by doing it once)
- Routine
- Tells one Bot when to run a job: on a schedule or when something happens. Runs in the cloud while your laptop is closed. Up to 50 per Bot. (source · tip: Keep routines one line long)
- Trigger
- The event that starts a routine: a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email to the Bot's address, or a webhook. (source · tip: Make routines cheaper: events, slow schedules, change checks)
- Test
- Runs a routine now instead of waiting for its schedule. It does real work, so use safe inputs. (source · tip: Do it by hand, save a skill, then schedule)
- Connector (app, plugin)
- A structured connection to a service like Gmail, Notion or Slack, added from Connect apps. Usually more reliable and cheaper than clicking through a website. Connected apps are available to every Bot on your account. (source · tip: Connectors before the browser)
- The Bot's computer
- A persistent cloud computer with a browser, files and a terminal. All your Bots share it, including signed-in sessions, so it is not a security boundary between Bots. (source · tip: A safety baseline before sharing logins)
- Take over
- Hands you control of the Bot's computer for a password, two-factor code, CAPTCHA or payment check. Choose I'm done to hand it back. (source · tip: Open your Bot's screen to watch or help)
- Secure Form
- A form in the chat where you type a login, card or address. The Bot fills it into the page without seeing secret values. (source · tip: Vault: logins, cards and contact info)
- Vault
- Settings, Vault: saved logins, cards and contact info your Bots can use without seeing passwords or card numbers. Covers your whole account, not one Bot. Not available on Team Bots. (source · tip: Vault: logins, cards and contact info)
- Secrets
- Where API keys and other non-login secrets go: the secure secret card in chat, or Secrets on a Team Bot. Values are write-only and never shown again. (source · tip: A safety baseline before sharing logins)
- Auto-review
- Checks a Bot's actions before they run. Add Ask first and Allow automatically rules under Settings, General, Auto-review. Ask first wins when both match. (source · tip: What actually stops a coding Bot (and what is only advice))
- Approval card
- Shows a proposed action with Allow once, Always allow and Deny. Cards from unattended work, such as routines, expire after about 30 minutes (since 0.77.0). (source · tip: Start each day with an approvals prompt, end it with a night prompt)
- Page
- A report, memo, dashboard or tracker a Bot builds for you. Private until you share it. Only the Bot can change it. (source · tip: Pages: reports and dashboards that stay up to date)
- Library
- A Bot's tab listing the Pages, files and apps it has made. Open it by clicking the Bot's name. You can pin items to the top. (source · tip: Pages: reports and dashboards that stay up to date)
- Bot email address
- A Bot can claim its own email address, receive mail and send from it. Routines can be triggered by mail to it, and tagged addresses like name+shop@ can have their own routine. (source · tip: Give your Bot its own email address)
- Cloud agent
- A Cursor coding agent your Bot can launch for coding work. A Project is a cloud agent that plans the work and runs its own agents. (source · tip: Watch coding work live and get recordings back)
- Grok Automations
- A separate Grok feature: describe a recurring job, schedule it or trigger it by email, and it runs as a fresh chat. Good for questions about public information that don't need a computer. (source · tip: Automations are not Grok Bot)
Next: your first week · troubleshooting