Advanced Handbook Introduction: Cloud Computer, Security, Networking, and Enterprise

Stage Goals

You can already get Grok Bot to do work, but a Bot is not a one-off script. Each Bot runs long-term on a persistent cloud computer — with a browser, file system, and terminal — and the cloud computer runs on Cursor's cloud. The longer you use it, the more you need to answer four questions:

• What to do when the computer is slow, broken, or in a bad state — maintenance
• Who watches over accounts, credentials, and files — security
• Whose network the Bot's traffic goes through, and whether it can touch your local machine — networking
• How to handle team sharing and company-wide management — enterprise

The Grok Bot advanced stage unfolds along these four threads. The goal is to upgrade from "can use" to "can manage": you can recover from problems yourself, sensitive data has a clear owner, you decide which path the traffic takes, and there is a path for team onboarding.

Course Roadmap

1. Cloud Computer Maintenance: Update, Recover, Reset, and data safety. What each of the three operations manages, and which data cannot be saved before a Reset — this is the foundation of the whole stage and the content of the next page.
2. Security and Credentials: the approvals mechanism, Vault (introduced in version 0.75.2: it keeps your logins, cards, and contact information for you, so the Bot logs in and checks out on your behalf without seeing plaintext; the entry point is under Settings > Vault), and 1Password integration (rolling out gradually; go by what your account actually shows). The principle is to let the Bot do the work without letting it run around with your passwords in the open.
3. Traffic Routing and Local Execution: letting the Bot use your network and computer — "Route traffic through this computer" makes the Bot's browser use your desktop's network and IP, while "Execution on this computer" controls whether actions run on your local machine (asking each time by default); private/VPN addresses are blocked by default, and there is an official solution when a website won't open.
4. Teams and Enterprise: Getting Started with Teams (shared Bots, templates, and admin controls) and Enterprise IT Deployment (MDM, network allowlisting, identity integration). Enabling the Enterprise tier, unified management, and usage all point to "contact your account team," and team seats are priced the same as individual seats. Suitable for readers currently evaluating a purchase.

Learning Order

• Read in numbered order; lesson 1 is a prerequisite for the rest of the content.
• Haven't run through a complete workflow yet? Go back to Efficient Workflow Introduction: From One Task to Full Automation first.
• Just looking up a specific issue? Go to FAQ: Models, Limits, and the Official Line, then jump back to the relevant lesson.
• When troubleshooting, check the Grok Bot status line on status.cursor.com first; if that doesn't resolve it, email support@x.ai.
• The interface has built-in Simplified Chinese (the desktop app supports 20+ interface languages), so there is no English barrier. For topics like @bot regional restrictions, payment methods, and the official line on availability in mainland China, see Guide to Use in China: Registration, Payment, and Chinese Interface — that lesson only states what has been officially confirmed and makes no guesses.

Next-Step Entry Points

Go to lesson 1: Cloud Computer Maintenance: Update, Recover, Reset, and Data Safety.

Want to see real-world usage before diving deeper? Read Scenario Walkthroughs: Choose Your Path.