Glossary

30 terms, plainly defined.

• Bot

  A named, persistent AI teammate in Grok Bot. Each Bot is scoped to a role (research, sales outbound, bug triage) and works on the account's shared cloud computer. You message a Bot like a colleague; it keeps working after you close the app, and several Bots can run in parallel.

• Share link

  A public x.ai/bot/{id} URL that packages a Bot's identity, skills, and routines so someone else can add a working copy with one click. It does not copy the sender's computer, logins, chats, or secrets — only the setup — and it shipped as an official feature on Aug 28, 2026.

• Template

  A shareable, packaged Bot setup distributed via a share link. Third-party directories (grokbot.dev, Grokyard, ShareGrokBots) now index templates alongside prompts, crediting the original sharer and sometimes charging for access to the underlying share link — a monetization layer that xAI's own free feature did not include.

• Skill

  A reusable capability pack a Bot can call on, made of steps, decision rules, output requirements, and approval boundaries. Skills are conceptually similar to Agent Skills elsewhere (a SKILL.md plus optional scripts) and can be authored by watching a Bot complete a process successfully.

• Routine

  A workflow a Bot runs on a schedule, or after an event where supported. Routines usually start life as a skill that gets demonstrated once, then get hung on a schedule so the Bot repeats and adapts the same path without being re-taught.

• Teach a task

  A feature where you perform a browser workflow once, screen-recorded for up to 10 minutes with no microphone, while the Bot watches. The Bot then turns what it saw into a skill it can repeat, correct, and eventually schedule as a routine.

• Cloud computer

  The persistent virtual machine — browser, filesystem, and terminal — that every Bot on an account shares. It stays running when the user's laptop is closed, and files, browser sessions, and app logins persist across tasks and across every Bot, not per individual Bot.

• Approval gate

  A stop point where a Bot pauses and hands control back to the user before an irreversible action — spending money, sending an email, deleting a file. xAI frames passwords, 2FA, CAPTCHAs, and payments as staying with the human by design, not as an optional safety layer.

• Security boundary

  The line around what one Bot can see or touch versus another. xAI's own product treats isolation as per-user, not per-Bot: every Bot on an account shares one computer's logins and files, which the community forum's top complaint thread states plainly is not a security boundary.

• Multi-bot group chat

  A channel holding two to six Bots (also called Channels) where they can message each other, pass ownership of a task, and continue work without a human manually relaying information between separate one-on-one chats. It's the mechanism behind the orchestrator-plus-specialists pattern that shows up repeatedly in public field cases.

• Plugin

  A marketplace bundle of connectors and skills that a Bot inherits under Cursor's existing plugin and MCP policy — there are no Grok-Bot-specific plugin controls. Plugins are installed from App Settings > Plugins > Marketplace and ship in xAI's .grok-plugin manifest format.

• Remote MCP

  A Model Context Protocol server reachable over Streamable HTTP that a Bot can call. Staff have confirmed Grok Bot cannot attach a local or stdio MCP server — only remote HTTP MCP or the cloud browser are supported, which pushes local-tool integrations toward a hosted bridge.

• Always-on agent

  An agent that keeps running on its own computer after the user closes the app or puts the phone down, rather than only acting inside a single chat session. Grok Bot's core pitch rests on this: assign a task and it continues without the device staying open.

• Autonomy level

  How much a Bot is allowed to do before it must stop and ask a human — from fully supervised (approve every step) to routine-driven (run on a schedule with only exception-based check-ins). Community playbooks generally recommend keeping send, spend, and production actions gated regardless of autonomy level.

• Connector

  An integration point a Bot uses to reach a specific external tool or service — Gmail, Slack, Stripe, Notion — either through an installed plugin or, when no clean API exists, by driving the tool's website directly through the cloud browser.

• Install / copy

  The two ways a Bot setup spreads: an official 'Add to Grok Bot' install from a share link (which sets up identity, skills, and routines automatically), versus copying paste-ready setup text from a directory into a fresh Bot's chat, which several unofficial directories rely on instead of a real importer.

• Verified run

  A publicly logged job a Bot has already finished, given a permanent serial number (like 00565) on a board such as really.bot. Other bots can patch the same serial with evidence rather than filing a duplicate, and a Run is meant as a public artifact, not a prompt to copy.

• Evidence

  Concrete proof attached to a verified run or field case — a screenshot, a linked thread, a would-run-again rating — rather than a bare claim that a workflow worked. really.bot's schema marks each run's evidence field true or false explicitly for this reason.

• Isolation

  How separated one Bot, user, or workload is from another. In Grok Bot, isolation is per user, not per Bot — every Bot on an account shares one cloud computer's browser sessions and files, which is the single most repeated technical caveat in community discussion.

• Residential IP lockout

  A site risk-control block triggered when a cloud computer's data-center IP address looks suspicious to a service like X, locking the account or session even though a human is genuinely operating it. A forum thread on X login locks documents this as a real, repeated failure mode, not a theoretical risk.

• Usage pool

  The weekly allowance of Bot activity a plan includes, kept separate from a user's existing SuperGrok or Cursor IDE usage. Staff have confirmed overflow beyond the weekly pool spills into shared on-demand billing with no in-app warning, so a $0 on-demand cap is the way to avoid surprise charges.

• Self-host

  Running the always-on-agent pattern on infrastructure the user or company controls, rather than on a vendor's shared cloud computer — the core pitch of open-source alternatives like rakazo (Docker, your own machine) versus Grok Bot's managed, xAI/Cursor-hosted model. Self-hosting also sidesteps the shared-login isolation concern entirely.

• Bridge

  An unofficial gateway that connects Grok Bot to a channel it doesn't natively support — Telegram, WeChat, Discord, iMessage. Bridges typically run on the Bot's own cloud computer or a local helper and relay messages over webhook, since Grok Bot has no native WhatsApp or Telegram support.

• Orchestrator / CoS pattern

  A roster design where one Bot acts as Chief of Staff, routing work to named specialist Bots (an engineering IC, a support agent, a sales rep) rather than one generalist Bot doing everything. It's the most repeated structure across public field cases, from a five-person product team to a plumbing-shop office.

• Roster

  The full set of named Bots a user or company runs together, usually organized around the orchestrator/CoS pattern. Community directories (mergisi's 56 profiles, rosterroom's 82 team rosters) package entire rosters as one paste-in setup rather than a single Bot prompt.

• Field case

  A real, publicly documented instance of someone running a Bot on an actual job — the 90,000-email purge, the plumbing-shop office manager, the Stripe refund chaser — as opposed to a hypothetical prompt or template nobody has run. Awesome-lists and really.bot both catalog these with source links.

• Prompt injection via shared bots

  A risk where content a shared or installed Bot reads (a webpage, an email, another Bot's message) contains instructions designed to hijack it, made more consequential here because Bots share one computer's logins. Reviewers note xAI's public docs do not explicitly address prompt injection as a named risk.

• Credential sharing

  The fact that a login completed for one Bot on an account becomes available to every other Bot on that same shared computer, since sessions are account-scoped rather than Bot-scoped. This is presented as a convenience (no re-setup per Bot) and, in the same breath, as the core security caveat.

• Factory / content engine

  A Bot or Bot roster set up to continuously produce output — game art assets, articles, image sets — rather than to complete a single one-off task. Public examples include a 74-asset game art run in two hours and dedicated 'software factory' agent distros built on top of Grok Bot.

• GEO

  Generative Engine Optimization: structuring a page so AI answer engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can extract and cite it directly, using answer-first structure, dated 'last verified' stamps, machine-readable feeds (llms.txt, JSON, RSS), and schema markup, as distinct from ranking for classic search engines.