Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The product launched in beta on August 11, 2026, and expanded plan eligibility on August 26. The plan and usage information below was checked against current official documentation on October 3.
- Current eligibility includes paid individual Cursor plans, self-serve Teams, and linking an eligible personal SuperGrok or X Premium+ account. Enterprises need to verify organization enablement.
- Official support now includes macOS, Windows, Linux, iPhone, Android, and iPad, extending beyond the initially limited set of clients.
- For the first task, use one redacted document and specify the output, sources, and stopping point. Verify the result before connecting accounts or creating routines.
- All Bots share the user's files and signed-in sessions. If a task stops responding, check status, pending approvals, login, and usage first. Preserve the current state instead of resetting the computer.
What Grok Bot is and which tasks to assign
Here, Grok Bot means the official AI teammate product with a persistent cloud execution environment. It can use authorized tools and websites, handle files, and let multiple Bots divide work. It should not be confused with @grok replies in X posts, ordinary question-and-answer interfaces, or third-party bots with the same name. The official August 26 expansion announcement recalls the August 11 beta launch; eligibility below was checked against documentation accessible on October 3, 2026.
To decide whether a task suits a Bot, first ask whether it has clear input and a verifiable output. This article recommends starting with organizing material, comparing sources, or drafting work for review. For example, ask one research Bot to extract effective dates from specified announcements and another to check omissions. This is an operating suggestion, not a result tested for this article or a claim that every Bot conclusion is reliable.
Eligible plans: check the current plan page
Cursor's official plan page lists Pro, Pro+, Ultra, and self-serve Teams. Personal SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ accounts can also be linked. SuperGrok Lite does not include eligibility, and SuperGrok Team and Enterprise do not support personal account linking. Self-serve Teams does not require a Premium seat first, although legacy request-based plans and Legacy Privacy Mode still have exceptions. Cursor plan allowances and linked-account allowances do not stack. With on-demand enabled, additional charges may arise after the weekly allowance is exhausted.
Enterprise documentation has different update dates: the September 29 FAQ still describes gradual availability, while the October 1 team documentation describes administrators enabling access and managing member scope through the Cursor dashboard. The plan page asks users to contact their account representative. It is therefore not possible to say that every Enterprise organization has access. Ask an administrator to confirm the current organization page and contractual eligibility. This article does not recommend changing organizational data policies without authorization merely to obtain access.
Getting started: install, sign in, and create the first Bot
Download Grok Bot from the official entry point and choose the version for your device. The FAQ lists macOS, Windows, and Linux; mobile requirements are iOS 18 or later and Android 9 or later. iPad uses the iOS app and requires iPadOS 18 or later. Sign in with the correct Cursor account and complete your organization's SSO flow if applicable. If eligibility comes through SuperGrok or X Premium+, complete linking as directed on the plan page. That page says this eligibility link cannot be removed or transferred to another Cursor account once created, so confirm the identity before continuing.
After initial setup, choose a suggested teammate or select Create your own to create a Bot. Start with one main responsibility instead of combining research, external sending, and account administration in one task. This article suggests defining the first Bot as a source-checking assistant: read only specified material, identify missing evidence, and stop before changing originals or sending anything externally. Selecting frequently used tools during setup does not itself authorize connections to those tools.
Writing the first task and verifying that it is complete
Start by uploading meeting notes without sensitive information and use a request such as: “Find three decisions that need my confirmation this week. For each, give the location in the original text and the deadline; if no date is provided, write Unspecified. Return only a task table. Do not edit the original or send anything to anyone.” This exercise was designed for this article to check sources and formatting, without promising speed or accuracy.
After receiving the result, check every date, owner, and source location against the original material. Ask the Bot for missing evidence instead of turning guesses into facts. When connecting a website next, confirm the target account first. If a password, two-factor verification, or CAPTCHA is required, take over Agent Computer to complete it, then return control. Consider saving a skill or routine only after the repeated process is stable, instead of enabling ongoing automation on the first attempt.
What multiple Bots share and what routines do
Current official documentation assigns one persistent cloud computer to each user. All that user's Bots share files, browser sessions, and signed-in accounts. Separate roles and conversations are not account isolation boundaries; assume other Bots may use services signed in on that computer. Closing the client does not stop tasks already running in the cloud.
A skill describes how to perform a task; a routine determines which Bot runs a workflow and when. Define acceptance criteria for a one-off task before setting its schedule and review method. Parallel tasks should avoid editing the same material simultaneously. If work requires separate computers and credentials, official team documentation recommends separate Cursor users, rather than simply creating another Bot.
Define authorization and approval boundaries before connecting real tools
Use the minimum permissions necessary and write clear stopping conditions for sending, publishing, deleting, paying, and changing permissions. Official Auto-review supports Ask first rules. Whether execution pauses also depends on the tool, action, and rule execution settings; a sentence saying “ask me before acting” is not account isolation or an absolute guarantee.
Before approving, verify the target account, object, content, and impact. Afterwards, inspect actual records in the target system instead of relying only on the Bot's completion statement. When a test no longer needs an account, sign out of its session on the shared computer and revoke authorization through the source service's controls. Deliverables should include verifiable files or source links so omissions can be found and corrected.
Troubleshooting missing access or an unresponsive Bot
First check the plan, current Cursor identity, organization policies, and client version. If a task has started but is not responding, inspect sidebar and conversation status and the official service status page. Then open the cloud computer to see whether it is waiting for approval, login, a verification code, or a user answer, and check whether usage is exhausted. Preserve the original task and error time and give only a brief corrective instruction. Do not assume a disconnected client means work has stopped.
If the cloud computer is unreachable, official guidance starts with Retry, reopening the conversation, and restarting the app, followed by Recover computer or Update where available. Do not start with Reset: recovery and updates preserve persistent files and logins, while a reset may lose recently unsynchronized work. Investigate the network separately only when a DNS, TLS, timeout, or proxy error is explicit. Changing networks cannot resolve eligibility, organizational permissions, or pending approvals.
Sources
- Official announcement: Grok Bot expands plan availability (2026-08-26)
- Cursor: Grok Bot plans and billing
- Official documentation: Get started
- Official FAQ: devices, shared computers, and workflows
- Official documentation: Teams and enterprises
- Official documentation: Approvals, security, and privacy
- Official documentation: Troubleshooting
- Cursor service status
Frequently Asked Questions
What is Grok Bot, and how does it differ from a chatbot?
It is an AI teammate product that performs tasks using tools, websites, and files in the cloud. Beyond asking questions, users can assign work with clear sources and acceptance criteria. Results still need verification.
How do I use GrokBot, and what should I do first?
Confirm eligibility, install the official client, sign in with the correct Cursor account, and create a Bot. Start with redacted material and request a task list with locations in the original text. Verify the output before connecting more tools.
Do I need the most expensive plan?
No. The current official plan page includes eligibility through Cursor Pro and the basic personal SuperGrok plan, among others. For linking, usage, and organizational exceptions, consult the official plan page listed here and your account interface.
Can creating another Bot isolate a different account?
No. A user's Bots share the cloud computer, files, and signed-in sessions. Another Bot divides responsibilities but does not create an account security boundary.
Are Linux, Android, and iPad supported?
Yes. The current FAQ lists Linux, Android 9 or later, and iPad running iPadOS 18 or later. Still verify version and device requirements when downloading.
Should I immediately Reset when Grok Bot is stuck?
Do not reset first. Check for pending approvals or login and exhausted usage. If the cloud computer is unreachable, follow the official retry, recovery, or update sequence. Resetting may lose recently unsynchronized work.