Grok Bot

Plugins connect Gmail, Notion, Slack and other services under the account used to sign in, added from Connect apps in the desktop sidebar, the mobile app or an in chat card. Beyond plugins, a Bot logs in once to tools such as Zendesk on its own computer and works inside them the way a person would, including tools that are hard to navigate. Bots can also claim their own address on mail.grokbot.com to receive, search and send email.

Sourcecursor.com/help/grok-bot/connect-pluginsread 2026-10-12

A user creates several Bots, one per project or function, and gathers them in a group chat, where they answer in the thread, take requests addressed to one Bot with an @mention, and message each other directly to hand off work. Bots carry a project from start to end, launch subagents and cloud agents, and run routines a user can teach by doing a workflow once while a Bot follows along. Because all of a user's Bots share one computer, files, browser and logins, a handoff keeps its context.

Sourcex.ai/botread 2026-10-12

Bots work from the files on their shared computer, the services connected through plugins and the tools they sign in to, reading what each task needs as it runs, and a Team Bot can carry a description and secrets its owner sets up for the whole team. There is no curated knowledge base or search index that a team maintains for its Bots.

Sourcex.ai/botread 2026-10-12

When an action needs approval, the conversation shows the proposed operation and its inputs, and the user picks allow once, always allow, which can save a matching rule, or deny, with the same controls on iPhone.

Auto Review, an independent review model, checks risky actions before they run, covering shell commands, plugin calls, computer use, changes to routines and triggers, and subagent launches, and it lets them proceed, holds them for approval or stops them.

Members can add their own check first rules, and Enterprise admins can enforce Auto Review with team rules members cannot switch off.

Sourcecursor.com/docs/grok-bot/securityread 2026-10-12

Grok Bot uses Cursor's sign in, auth and Privacy Mode, with SAML or OIDC single sign on on Teams Premium, and SCIM, the MCP allowlist and organization computer management on Enterprise. Admins control network destinations, team secrets, setup scripts, sudo on Bot computers and action recording, and API keys go into masked secret cards that keep the value out of chat and files. Anysphere, the company behind Cursor, holds ISO 27001 and ISO 42001 certification from Schellman with Grok Bot in the current scope, and data is deleted or returned within 30 days of written direction under the DPA.

Sourcecursor.com/docs/grok-bot/securityread 2026-10-12

Enterprise teams get audit logs and OpenTelemetry export of Bot activity, and admins can switch on action recording for team computers. In every plan, the conversation shows each operation awaiting approval with its inputs, and Teams plans add shared usage analytics. Usage and spending views count Bot work as Grok Bot usage, without naming the model behind each request.

Sourcecursor.com/docs/grok-bot/securityread 2026-10-12

Each Bot keeps context on how its user works and updates its own memory as it learns, such as noting that a customer only signs annual contracts and who approves them, and a user can make a standing rule by asking a Bot to remember it. Bots also learn from one another, and the shared computer keeps files, browser state and logins between runs while chats are stored separately. A user gets no retention period for a Bot's memory and no way to review or remove a single entry.

Sourcex.ai/botread 2026-10-12

Each member gets one hosted microVM in the US, reached through Cursor's servers, with internet traffic leaving through static egress addresses shared across customers. Enterprise teams can route a computer's traffic through a member's desktop, install their own networking client or set proxies and TLS inspection, which connects the cloud computer to private networks without moving it. There is no region choice or deployment inside a customer's own environment.

Sourcecursor.com/docs/grok-bot/securityread 2026-10-12

A marketplace offers ready made Bots, each built for one role, among them Sales Outbound, Talent Scout, Paid Media, Expense Manager, Product Performance, Bug Reproduction, Account Health and Chief of Staff. Sales Outbound, for one, researches accounts overnight, ranks contacts by intent and drafts email and LinkedIn messages in the user's voice for review. A Bot's identity, skills and routines can be shared as a public link for others to copy, owners can publish a Team Bot that every teammate chats with privately, and Teams plans add a team marketplace for skills and plugins.

Sourcex.ai/botread 2026-10-12

A routine tells a Bot when to run a workflow, either on a schedule or when something happens, such as a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email or a webhook call. Routines run in the cloud while the user's laptop is closed and can be paused or resumed from the Bot's details. Users also message Bots from macOS, Windows and the iOS app, talk to them by voice, and email them at their own address.

Sourcecursor.com/help/grok-bot/routinesread 2026-10-12

For each task, Grok Bot picks the model most likely to do it well, an xAI model or a third party model from a provider on the subprocessor list, and the choice can change from one request to the next. Users cannot see, choose or block a model, there is no model picker, and a team's Cursor model allowlist does not apply to Grok Bot.

Sourcecursor.com/help/grok-bot/modelsread 2026-10-12

Outside systems reach a Bot through a routine started by a webhook call, with the routine's own URL and key shown on its details. That is the one inbound path. There is no public API or SDK for creating Bots, sending them work or reading their results, and MCP plugins point outward to other services.

Sourcecursor.com/help/grok-bot/routinesread 2026-10-12

Auto Review judges each risky action as it happens, a guardrail on behavior, and a taught routine is saved from a single demonstration. Neither tests a Bot's output. There are no test cases, quality checks or comparisons of a Bot's results before or after a change.

Sourcecursor.com/docs/grok-bot/securityread 2026-10-12

Bots share a persistent cloud computer with files, a browser, installed apps and saved logins, sign in to a team's apps and websites and use them the way a person does, including tools that are hard to navigate. When a site blocks cloud traffic, the Bot hands the step to the user or routes its traffic through the user's desktop, and with permission it can run commands on that desktop, asking before each one by default. Settings can update, recover or reset the cloud computer, keeping saved Bots, files and logins.

Sourcex.ai/botread 2026-10-12