Grok Bot

A Bot is not a longer chat. You message it (type, dictate, or voice). It does multi-step work inside the tools you already use, posts updates — including drafts and voice memos — and only stops you for a judgment call. Work continues with the app, laptop, or phone closed.

When a Bot fits

Access

• Desktop app: macOS (Apple silicon and Intel), Windows (x64 and Arm64), Linux (x64 and Arm64).
• Mobile: iPhone, iPad (iPadOS 18+), Android 9+.
• Included with paid individual Cursor plans and Cursor Teams, or by linking SuperGrok, SuperGrok Plus, or SuperGrok Heavy. Usage is its own weekly allowance, separate from chat.
• Org SSO follows the normal Cursor sign-in. The computer runs in Cursor’s cloud.

One computer, many screens

Every Bot on your account shares one persistent cloud computer: browser cookies, files, and command-line credentials. Isolation is between users, not between your Bots. Each Bot gets its own screen, so several can click around at once — but one Bot runs only one computer-use task on its screen at a time.

• Open Agent Computer from a conversation to watch clicks, typing, and navigation. You can leave the preview; the job continues.
• Sessions persist, so you usually sign in once. Signing in for one Bot signs in the others. Some sites still expire sessions or demand a human check — the Bot should pause and ask, not bypass it.
• Do not put a credential on the computer if another Bot on the account should not have it. Separate Bots are not a security boundary.

How you talk to it

• Paste text, links, and images. Attach local files.
• Dictate: desktop Cmd/Ctrl+D or Start voice input — it types into the composer so you can edit before send. On phones, Start dictation.
• Voice chat: Start voice chat on an empty composer (desktop, iPhone, Android).
• Voice memos: a Bot can reply with audio. Play it, or expand for the transcript.
• / references a saved skill. @ mentions a Bot, group, routine, or connector.
• Search (where rolled out) finds Bots, groups, messages, files, links, and routines.

A strong first task names the outcome, the sources, and the constraint:

Outcome: a weekday watch list of accounts that slipped.
Sources: the CRM export in Drive and yesterday’s support mail.
Constraints: never email a customer. If the export is missing, say so —
do not reuse last week’s file.
Done when: five bullets, each with a source link, posted in this chat.

Connectors before clicking

Install plugins from Marketplace in the sidebar (Add → OAuth). In chat, @ the connector onto the task. Prefer a connector over computer-use when one exists — it is more reliable than clicking through a website. Computer use is the fallback for tools with no API, and for anything the connector cannot reach.

Skills, then routines

Make the one-time task reliable first. Then save the method. Only then automate it.

Save the process we just used as a skill called “Weekly account health.”
Include the source systems, the risk rules, the output format,
and the rule that customer contact always requires my approval.

Every weekday at 8:00, run Daily customer-risk against the current account list.
Post a linked watch list in this conversation. Do not contact customers.
If the source is unavailable, report the failure. Do not use old data.

A skill worth keeping states:

1. When to use it
2. Required inputs and access
3. The sequence
4. How to validate
5. What to return
6. What requires approval

Teach a task

When Teach a task is available, record one browser workflow from the computer view. The Bot drafts a skill from the recording. Review it, run it on a second input, and fix the failure cases before you attach a routine. A sloppy recording becomes a sloppy nightly job.

Bots coordinating

• Bots message each other and can sit in a group chat (small groups, on the order of two to six).
• They pass work and assign ownership. You are not the router between tools.
• Context moves through shared files, direct messages, the group, and explicit handoffs. A common shape is one coordinator plus a specialist per lane (inbox, expenses, bugs).
• For anything that matters, tell the Bot to check the live source. Memory is a summary, not a system of record.

Team Bots (Teams & Enterprise, public beta)

Launched 28 September 2026. A Team Bot is one shared coworker for a role, not a copy per employee. People use it alone or in Slack. The Bot is shared; each person’s conversations stay private.

Pre-built starting points exist for sales, product, marketing, and data. Team-level skills are shared; per-user chat context is not.

Approvals and the line you do not cross

• Drafts (mail, Slack, and similar) should come back for approval before anything is sent.
• Say the forbidden action in the skill: “never change production settings”, “never contact the customer”.
• If a site asks for a verification challenge, the Bot pauses and notifies you.
• Correct a lasting preference out loud. It will not infer a new rule from one annoyed message.
• Start a thread or a new Bot when the conversation has become a different long-lived job.