Grok Bot Glossary: Every Term You'll Meet, in Plain English

This glossary defines the Grok Bot terms you will meet in the app, docs and changelog, grouped by what they control. Definitions paraphrase docs.x.ai and Cursor's help as of October 2026; changelog-only terms are flagged. Hold onto one idea: every Bot on your account shares one computer.

At a glance: the ten terms that matter most#

Bots and how they relate#

Roles here organize work. They do not isolate access.

• Bot: a durable AI teammate with a name, a job, its own conversation, and working context that grows over time.
• Primary Bot: the starred Bot in your sidebar. Since 0.66.0 it can offer to take work off your plate. Changelog term; not yet in the docs. A Shared Bot cannot be primary (since 0.68.0).
• Helper Bot: a Bot that one of your Bots created to help with its work (Cursor's help).
• Group chat: two to six Bots working toward one outcome.
• Duplicate: a copy of a Bot with its profile, settings, skills, routines and avatar, but none of its conversation history or learned memory.
• Template: a shareable Bot recipe (identity, skills, routines). It never carries your computer, logins or history.
• Import Memory: since 0.77.0 (October 26), a Settings option that brings preferences and context from another AI assistant into your primary Bot. Needs 0.75.2 or later. Changelog term.

Team terms#

• Shared Bot (formerly Team Bot): one Bot your whole team uses, each person in a private chat, set up and shared by its owner. The docs used the new name by October 28; the October 26 changelog still said Team Bot. See our Shared Bots guide.
• Manager: a teammate allowed to change a shared Bot's setup; only the owner can delete it.
• Collaborator: a teammate who can only chat with a shared Bot.

The computer#

Where all Bot work happens. Our shared-computer guide explains what this means for logins.

• Agent Computer (Computer): the persistent cloud machine with browser, command line, files and connected tools. One per user, shared by all of that user's Bots.
• /workspace: the shared folder where Bots keep durable project files. Every Bot on the account can read it.
• Take over: controlling the Bot's computer yourself, say for a password or CAPTCHA, then handing it back.
• Watching / Take control: since the October 11 changelog entry (0.69.0 to 0.70.2), full-screen view opens in Watching mode, view-only, until you press Take control. Changelog terms.
• Wake: rousing a sleeping computer. Since 0.71.2 you click the "Computer is asleep" preview to wake it in place. Changelog.
• Recover, Update, Reset: recovery controls, mildest first. Recover and Update keep durable files and logins. Reset restores the last saved snapshot and can lose recent work.
• Execution on Local Computer: whether Bots may run commands on the machine in front of you. Ask every time (default), Always allow, or Never allow.

Repeatable work#

How a one-off request becomes something that runs on its own. Compare the two core ideas in skills vs routines.

Outputs and extras#

• Page: a styled report, memo, dashboard or tracker a Bot builds and can keep updated, even from a routine. Canvases and documents became Pages in the October 11 changelog; Pages headlined 0.75.2 (October 22). Shared Pages offer Download (PDF) and Share. See our Pages guide.
• Library / Pinned: your past Pages, files and links; since 0.75.2 pinned items stay on top.
• X search: read-only access to public X posts, profiles and trends without connecting an X account.
• @bot on X: tag @bot in a post to hand it to your main Bot as a task. Not yet available in the EU, the UK, Australia and a few other countries.
• Project: a Cloud Agent a Bot can start that plans work and runs its own agents (changelog 0.57.0).
• Cloud Agent: Cursor's coding agent on separate computers. Bots can hand it coding tasks, billed to your Cursor plan.

Apps, sign-ins and secrets#

How Bots reach your tools. The full picture is in our plugins and MCP guide.

• Plugin (connector): a structured connection to a service such as Gmail, Slack or Notion. Installed once, available to every Bot; tokens stay on Cursor's backend.
• Connect Apps: where you find and install plugins; called Marketplace until 0.67.0 (October 2). Open it from the sidebar or with Cmd/Ctrl+Shift+M. Bot templates moved to the web Marketplace at x.ai/bot/marketplace.
• Agent email: an address at mail.grokbot.com for receiving, searching, sending and, since 0.75.5, forwarding mail. One per account, shared by all Bots, and permanent. Chat-requested sends go out once Auto-review allows; routine sends wait on a draft card. On a Cursor team, an admin enables it first.
• Custom MCP server: a Model Context Protocol server you add by asking a Bot in chat; it must be reachable over public HTTPS.
• Secret request: a secure card for entering a key or token. The value is masked, kept out of the transcript and hidden from the model.
• Secure Form: the in-chat form a Bot uses to fill something you type into a web page. In October a password entered this way appeared in a page snapshot; no fix was confirmed by October 14.
• 1Password: lets a Bot sign in with your saved logins. Since 0.77.0 it connects without a shared vault, and you approve each login in 1Password.
• Vault: since 0.75.5 (October 23), stores logins, cards and contact info so Bots can sign in or check out without seeing secrets. Covers every Bot, unsupported on Shared Bots. 0.77.0 added a Payments tab; 0.78.1 lets Shop Pay connect there.

Approvals and safety#

What stops a Bot before it acts. Our permissions guide turns these into a worksheet.

• Approval card: a proposed action with Allow once, Always allow (can save a rule) and Deny. Since 0.75.5, a denied action is not retried until you send a new message.
• Auto Review: an independent model that checks risky actions (shell commands, plugin calls, computer use) before they run. Since 0.75.8 it double-checks before showing a card, so fewer safe actions need approval.
• Ask first rule: always stops matching actions. Beats an Allow automatically rule when both match.
• Custom Rules: Settings' name for saved approval rules since 0.68.0; since 0.75.8 a Bot can propose changes you confirm.
• Permissions: since 0.77.0, the Settings section listing rules under Always Ask and Allow without Asking. Approval cards now stay open 30 minutes instead of 10.
• Draft card: an editable email or Slack message to send or discard.
• Privacy Mode: Cursor's data setting under which customer data is not used for training. Legacy Privacy Mode, which stores nothing, does not work with Grok Bot.

Plans and usage#

Since October 12, 2026 new customers buy The X Subscription; older Cursor and SuperGrok plans continue. Prices are in our pricing guide.

The X Subscription terms#

• The X Subscription: SpaceXSI's single plan for Grok, Grok Bot, Cursor and X Premium benefits. Grok Bot is on Premium, Super, Ultra, Teams and Enterprise, not Free or Plus.
• Shared weekly pool: one weekly allowance per paid seat covering Grok, Grok Bot and Cursor together.
• Top-up / Additional Usage: prepaid credit for use beyond the pool and for third-party models in Cursor. Auto Top-up is off unless you turn it on.
• Monthly additional usage limit: the spending cap on Additional Usage per calendar month; the docs call it the hard stop.
• Unify (switch): combining existing Cursor, Grok and X accounts under The X Subscription. Optional and permanent; old web subscriptions are refunded pro rata.

Older-plan terms#

• Legacy plan: Cursor's label for its pre-October 12 plans.
• Weekly usage: the included Grok Bot allowance on older plans, measured in agent steps and tokens, reset weekly.
• On-demand usage: opt-in extra usage after the weekly allowance, capped by a monthly limit a running task can overshoot.
• Usage-credit trial: Cursor's free trial, a usage credit with a 7-day window that never becomes a paid plan.
• SuperGrok link: connecting SuperGrok or X Premium+ to grant Grok Bot usage to a Cursor account. Permanent and non-stacking; same tier as Pro.
• Grok Business seat: a self-serve Grok Business seat that includes Grok Bot, used via Sign in with Grok rather than linking.

Terms people mix up#

Our take#

Learn three distinctions and the rest of Grok Bot's vocabulary falls into place: skill versus routine, plugin versus browser sign-in, and Recover versus Reset. Treat every "separate" Bot as sharing your computer, folder and Vault, and set approval rules accordingly. New here? Start with what Grok Bot is.

Frequently asked questions#

What is the difference between a skill and a routine in Grok Bot?#

A skill is a reusable set of instructions describing how to do a task, stored in one library shared by all your Bots. A routine tells one specific Bot when to run a workflow, either on a schedule or after an event such as a Slack message or incoming email. Save the method as a skill first, then add a routine once it works reliably.

Are a plugin and a connector the same thing?#

Yes, in practice. The docs say connectors are installed as plugins, and the app calls them plugins. You find and install them in Connect Apps, which was called Marketplace until version 0.67.0 on October 2, 2026. A plugin installed once is available to every Bot on your account.

What is a primary Bot?#

It is the Bot marked with a star in your sidebar. The 0.66.0 changelog says it can now spot work it could take off your plate and offer to handle it. The official docs did not define the term yet when we checked, and since 0.68.0 a Shared Bot cannot be your primary Bot.

What is the difference between a Team Bot and a Shared Bot?#

They are the same feature under two names. A Shared Bot is one Bot your whole team talks to, each person in a private chat, set up and shared by its owner. The official docs had renamed Team Bots to Shared Bots by October 28, 2026, while the changelog entry of October 26 still said Team Bot.

What does Vault do in Grok Bot?#

Vault, added in 0.75.5 on October 23, stores logins, cards and contact info under Settings so a Bot can sign in or check out without seeing the saved password, card number or security code. It needs Grok Bot 0.75.2 or later, covers every Bot on your account, and is not supported on Shared Bots.