Documentation 2026-09-07 22:57 UTC to 2026-09-11 21:00 UTC

2 2 

3# Grok Bot3# Grok Bot

4 4 

5Bots are AI teammates you can give real work to. Bots can sign and use apps and5Grok Bot gives you Bots you can keep around: AI teammates with names, jobs, and

6websites just like you do on a persistent cloud computer. They can collaborate6context that compounds over time. Each Bot works on a persistent cloud computer

7independently, passing context between each other and handing off tasks, and7with a browser, filesystem, and terminal, so tasks finish in your real tools

8understand the nuances of how you like work done over time. They finish jobs8instead of as chat drafts. [Get started](/grok-bot/get-started) with your first

9end to end, and only come back when something needs your approval.9Bot, or read [how teams roll it out](/grok-bot/teams-and-enterprises).

10 10 

11You work with a Bot by messaging it like a teammate. Give it a task or function,11You work with a Bot by messaging it. Give it a task, the relevant context, and

12relevant context, and access to any tools or files needed to do the work. Bots12access to the tools it needs. It takes on multi-step work across apps and

13take on ambitious projects, work across multiple tools and systems, and keep you13websites, keeps you updated in the conversation, and comes back when something

14updated of their actions in the conversation.14needs your approval.

15 15 

16> In the Docs and in the Grok Bot app, a Bot = a single persistent, named agent16Grok Bot runs on macOS, Windows, Linux, iOS, and Android, and is included with

17> or one AI teammate.17every paid individual Cursor plan and with the Cursor Teams plan. You can also

18link an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription.

19See [Plans and billing](https://cursor.com/help/grok-bot/plans) for the full

20matrix.

18 21 

19## What makes Grok Bot different22## What makes Grok Bot different

20 23 

21* **It has a computer of its own.** Each Bot runs on a persistent cloud VM with24* **Each Bot has a computer.** Your Bots run on a persistent cloud computer with

22 a browser, filesystem, and terminal. It can use connectors/MCP where25 a browser, filesystem, and terminal. They use

23 available, and computer use for apps and websites without a clean API, so work26 [connectors](/grok-bot/computer-and-apps#connect-an-app) where available and

24 finishes in the real tools rather than as chat drafts.27 computer use for everything else, and work continues while your laptop is

25* **It is very easy to get started.** Create a Bot, message it, and grant access28 closed.

26 as needed. No workflow builder or prior Bot setup required. The same Bot is29* **Setup is a message, not a workflow builder.** Create a Bot, describe the

27 reachable from the desktop and mobile apps.30 job, and grant access as it asks. The same Bot is reachable from the desktop

28* **It coordinates independently with other Bots.** Multiple Bots share one31 app and the [mobile app](/grok-bot/mobile).

29 user-scoped computer and can run in parallel. They can message each other,32* **Bots coordinate with each other.** Your Bots can run in parallel, message

30 share context in threads or group chats, and pass ownership so you are not the33 each other, share context in

31 router between tools.34 [group chats](/grok-bot/chat-and-collaboration#start-a-group-chat), and pass

32* **It can learn workflows from live demonstration.** Ask a Bot to follow along35 ownership of a task, so you aren't the router between tools.

33 once through a multi-step or multi-system path. It persists that path as a36* **Bots learn workflows from demonstration.** Walk a Bot through a multi-step

34 routine and can re-run it on a schedule or on demand.37 path once, and it can save the path as a

35* **It is a persistent, named teammate with a durable state.** Named Bots keep38 [skill](/grok-bot/skills-routines-and-automations) and rerun it on a schedule.

36 memory, files, browser sessions, and preferences across turns. Context39* **Context compounds.** A named Bot keeps its memory, files, browser sessions,

37 compounds instead of resetting to a fresh environment on every task.40 and preferences across sessions instead of resetting on every task.

38 41 

39## Bots share one computer42## Your Bots share one computer

40 43 

41All of your Bots use the same persistent cloud computer. They share files,44All of your Bots use the same cloud computer, sharing its files, browser

42browser sessions, and app logins, which makes handoffs possible without45sessions, and app logins, which makes handoffs work without repeating setup. The

43repeating setup.46computer belongs to your account, not to an individual Bot, so treat anything

44 47placed on it as available to every Bot you run; between users, isolation is

45The computer is isolated to your account, not to an individual Bot. Treat a48strict. [The computer and apps](/grok-bot/computer-and-apps) covers the full

46login or file placed on the computer as available to all of your Bots. Each Bot49model.

47gets its own screen on that computer, so several Bots can use browser and

48desktop tools in parallel without getting separate security boundaries.

49 50 

50## A good first handoff51## A good first handoff

51 52 

52Start with a real task that involves multiple tools and has a clear result:53Start with a real task that spans a few tools and has a clear finish line:

53 54 

54> Pull this week's Strategic Prospects PG List from Salesforce. Skip anyone55> Pull this week's pipeline review list from our CRM. Skip anyone already in an

55> already in a sequence. Research the top 5 accounts across the web, Slack,56> active sequence. Research the top five accounts across the web and Slack,

56> Databricks, and Sumble, pull contacts, and draft LinkedIn and email in my57> pull the right contacts, draft outreach in my voice, and leave me drafts to

57> voice, and leave me drafts to approve by tomorrow morning58> approve by tomorrow morning.

58 59 

59This tells the Bot what to do, where to work, what context to pull in, what60This tells the Bot what to do, where to work, what context to pull in, and what

60you'd like to see as a finished deliverable.61finished work looks like. Review the result, correct it, and turn the stable

61 62process into a [skill or routine](/grok-bot/skills-routines-and-automations).

62You can review a Bot's work, provide corrections, and turn the process into a63 

63reusable skill or proactive routine.64## FAQ

64 65 

65## What to explore next66### Does Grok Bot keep working when my laptop is closed?

66 67 

67* [Get started](/grok-bot/get-started) with the desktop app and your first Bot.68Yes. Work runs on the cloud computer. Closing the app, your laptop, or your

68* Discover more [use cases](/grok-bot/use-cases) for Bots.69phone doesn't stop a background turn or a routine.

69* Make recurring work repeatable with [skills and routines](/grok-bot/skills-routines-and-automations).70 

70* Learn how to [use the computer and apps](/grok-bot/computer-and-apps).71### Can several Bots work at the same time?

71* Review [approvals, security, and privacy](/grok-bot/approvals-security-and-privacy)72 

72 before granting access to sensitive systems.73Yes. Bots can reason, use connectors, work with files, and coordinate in

73 74parallel. Each Bot gets its own screen on the shared computer, and one Bot runs

74## For team admins and security reviewers75one computer-use task on its screen at a time.

75 76 

76The pages below cover rolling Grok Bot out for a team or organization:77### What does a Bot remember?

77 78 

78* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises) covers79Stable preferences, role context, and summaries of prior work. Conversations

79 the architecture, rollout steps, the admin controls and which plans include80and learned context stay separate per Bot, while shared files, browser

80 them, and the configuration Cursor recommends.81sessions, and direct handoffs move context between them. For consequential

81* [Grok Bot security](/grok-bot/security) and the82decisions, ask the Bot to check the current source instead of relying on

82 [Grok Bot security FAQ](/grok-bot/security-faq) cover network policy, egress,83memory.

83 approvals and Auto Review, identity, logging, data retention, hosting, and84 

84 certifications for security reviewers.85### Can a Bot use any website?

85* [Configure identity and access](/grok-bot/identity-and-access) walks through86 

86 Okta and Microsoft Entra ID: widening the Cursor app assignment beyond87Bots can use many browser-based tools, including services without a connector.

87 engineering and letting members sign in to IdP apps from the Bot's computer.88A site can still block automation, expire a session, or require a human step.

88* [Connect to private networks](/grok-bot/private-networks) shows how to reach89The Bot hands those steps to you rather than working around them.

89 internal services from team computers with Tailscale or Cloudflare Tunnel90 

90 through Team Setup.91### Which platforms are supported?

92 

93The desktop app runs on macOS (Apple silicon and Intel), Windows (x64 and

94Arm64), and Linux (x64 and Arm64), and the mobile app runs on iPhone and

95Android. The computers Bots work on run in Cursor's cloud.

96 

97### How much does Grok Bot cost?

98 

99Access is included with every paid individual Cursor plan and with the Cursor

100Teams plan, or through an individual SuperGrok account link. Usage resets

101weekly. See [Plans and billing](https://cursor.com/help/grok-bot/plans).

102 

103## Next steps

104 

105* [Get started](/grok-bot/get-started) — Install the app, create your first Bot, and hand it a useful task.

106 

107* [Use cases](/grok-bot/use-cases) — Roles that work well, with starter prompts you can adapt.

108 

109* [Work with Grok Bot](/grok-bot/bots) — Bots, messaging, the shared computer, and skills and routines, one page each.

110 

111* [Teams and Enterprise](/grok-bot/teams-and-enterprises) — Admin controls, identity, private networks, and the recommended rollout baseline.

112 

113* [Security](/grok-bot/security) — Network policy, approvals and Auto Review, logging, and data handling.