Reference
Grok Bot glossary
People bounce between five words — Bot, computer, skill, routine, plugin — and treat them as one. They are not. Use this page when a tutorial collapses them, then return to the lesson that owns the job.
- Grok Bot
- The official app from xAI / SpaceXAI with Cursor: a roster of named teammates plus one shared cloud computer. Not grok.com chat.
- Bot
- One named teammate on your roster. It has a screen on the shared computer. Creating another Bot is not a security boundary.
- Computer
- The persistent cloud machine assigned to your account. Browser, files, and terminal live here. Every Bot can see the same logins and cookies.
- Screen
- The work surface one Bot uses on that computer. Parallel screens are not isolation. One computer-use task runs per screen.
- Skill
- A reusable how: when to use it, inputs, steps, how to verify, what to return, and what needs approval. Save after a good run.
- Routine
- A when: schedule or event on one Bot. Tests do real things. Put sends, deletes, and payments behind approval.
- Teach a task
- Desktop recording of about ten minutes of screen actions (no microphone). The Bot drafts a skill. You still add stop rules.
- Plugin / connector
- Account-level integration. Prefer a connector over clicking the web. Installed for the account, not locked to one Bot.
- MCP
- Remote HTTP tools the computer can call. Localhost / stdio MCP on your laptop is unreachable from the cloud machine.
- Share / template
- A public x.ai/bot link that copies identity, skills, and routines — not your computer or logins. Strip secrets before sharing.
- Chief of Staff
- Community convention: one pinned Bot you talk to. It proposes specialists. Official docs only require name, job, and how it works.
- Require Approval
- The human gate for sends, spend, and other writes. Description beats shouting stop later in chat.
- Weekly usage
- Meter on the Cursor account. macOS and iOS share one bucket. Exhaustion can spill into On-Demand if that is enabled.
- On-Demand
- Shared paid overflow after the weekly pool. The app may not warn you in-product. Watch the Cursor usage screen.
- Cursor account
- The only login. There is no separate Grok Bot account. The same account holds the plan and the usage meter. Grok Bot is not a Cursor IDE panel.
- Hermes
- A different named-bot host. Some skill packs port a roster there. A Hermes profile is not a Cursor Grok Bot.
- grok.com / Grok
- Chat, Imagine, and Voice. Google often ranks it for “grok bot.” Wrong product for this handbook.
- Grok Build
- Local coding CLI. Not Grok Bot. The community app grok-app is a GUI for Grok Build, not a Bot client.
- Legacy Privacy Mode
- A Cursor setting that can block Grok Bot computer provisioning. Turn it off on the account you sign in with.
Common collisions
Is a skill the same as a plugin?
No. A skill is written instructions. A plugin or connector is an account-level integration that gives the computer real tools. You usually need both.
If I create a second Bot, are my logins isolated?
No. Isolation is per user, not per Bot. Files, cookies, and sessions on the shared computer are visible to the whole roster.
Does a share link copy my computer?
No. Official share copies identity, skills, and routines. It does not copy the cloud computer or the logins stored there.
Is Grok Build a Grok Bot client?
No. Grok Build is a local coding CLI. grok-app is a desktop GUI for that CLI. Install Grok Bot from x.ai/bot.
Next: what Grok Bot is, skills and routines, or official vs alternatives.