Grok Bot Setup: 7 Steps From Install to Your First Routine

Check plan & privacy → Install & sign in → Define one job → Hand a 5-part first task → Connect apps → Set approval boundaries → Save as skill & schedule routine

Who

Working users on a paid Cursor plan or SuperGrok who want Grok Bot to handle daily repetitive tasks

You get

Install Grok Bot desktop, create your first Bot, connect apps, configure approvals, and run a reusable Routine

You need

Grok Bot

Steps

1. Check plan and privacy setting, then install

   Verify your Cursor plan includes Grok Bot (paid individual, Teams, any SuperGrok tier, or Grok Business self-serve seat). If your account is on Legacy Privacy Mode, switch to a supported cursor.com data setting first. Download the desktop client for your platform: on Mac choose Apple Silicon or Intel and drag to Applications; on Windows choose x64 or Arm64 and run the installer; on Linux pick .deb, .rpm, or AppImage. The app checks for updates automatically; you can also use Check for Updates in Settings.

2. Sign in with your cursor.com account

   Choose Sign in on the welcome screen, complete cursor.com authentication in the browser window, then return to the app. If your access comes through SuperGrok, link it when prompted. On first use you click through a short intro while cloud computer setup runs in the background. Grok Bot then creates your first Bot, named Grok Bot, and opens a chat. No workflow builder is needed.

3. Give your Bot one job

   Tell the Bot its primary job in the first message and ask it to remember how it should work. Official guidance recommends a focused role, for example: "Your job is product performance... Preserve links and screenshots, separate evidence from hypotheses... Never change production settings. Remember this for future work." When work splits into different roles, add more Bots via New → Create new Bot.

4. Hand it a first task with five parts

   A strong request includes: outcome, sources, constraints, deliverable, and review point. For a quick first win, attach a document you already know well and ask for a five-bullet summary, with every date, decision, and open question listed separately, a page or section cited for each, and the source file left unchanged. Type or dictate on desktop with Cmd/Ctrl+D. Then name lasting preferences, for example: five bullets, source links inline, and a final section called "Decisions needed."

5. Connect your apps and keep passwords private

   Open Connect apps in the sidebar, find an app, choose Add, and finish the provider login in your browser. Then type @ in chat to attach the app to your task. OAuth tokens are held on cursor.com's connector backend; the Bot uses tools without receiving credentials. If a site needs a password, passkey, 2FA code, or CAPTCHA, choose Take over, complete the step yourself, then choose I'm done. The Bot does not see your password. Since v0.75.5 you can also save logins, cards, and contact info in Settings → Vault; the Bot fills them in but never sees saved passwords, card numbers, or security codes.

6. Set your approval boundaries

   State in the request where the Bot must stop. Official docs list sending messages, publishing, purchases, deleting data, changing permissions, production changes, and accepting legal terms as good places for explicit boundaries. Each approval card shows the proposed action; choose Allow once, Always allow, or Deny. In Settings → General → Auto-review, add rules such as "Ask first before sending any external email." When Ask first and Allow automatically both match, Ask first wins. Under Settings → Computer, "Execution on this computer" defaults to Ask every time. All Bots share one cloud computer, files, and browser sessions, so separate Bots should not be used as a security boundary.

7. Turn what works into a skill, then a routine

   Official advice: make a one-time task reliable, save the method as a skill, and only then automate it. A good skill states when to use it, inputs, steps, how to validate the result, what to return, and what needs approval. Then ask the Bot that owns the job for a routine, for example every weekday at 8:00 AM. Confirm owner, schedule, time zone, input source, expected result, and approval boundary. Use Test before switching it on; a test run does real work, so use safe inputs. Routines run while your laptop is closed. A Bot can own up to 50 routines, and schedules must be at least five minutes apart.

No prompt needed — just follow the steps.