How to set up Grok Bot comes down to three moves: create one bot, connect your plugins in a sensible order, then let that first bot design the rest of your team. The whole setup takes about ten minutes. The order you do it in decides how useful it feels by day three. This guide walks through each step, plus the specific mistakes real early users hit before they found a routine that worked.
A note on scope: this covers getting a working team running, not whether you should connect it to anything sensitive. Shared sessions across bots, banking or payroll credentials, and what SpaceXAI's own documentation says about liability are covered in our companion article on what Grok Bot actually is. Read that first if you haven't. The credential sharing described below is real and by design, not a bug.
Grok Bot doesn't hand you a blank chat box. Every plugin you add and every bot you name sticks around and keeps working while you do something else. That's the point. It's also why the order matters more than you'd expect.
Before you open the app
Grok Bot comes with every paid individual Cursor plan and with the Cursor Teams plan (Standard and Premium seats). If you pay for Grok instead, you can link an individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy subscription to your Cursor account. There's no standalone Grok Bot subscription. Enterprise access goes through SpaceXAI sales, according to the official Grok Bot page.
You sign in with a Cursor account either way. One catch: Grok Bot needs cloud data storage, so accounts still on Cursor's Legacy Privacy Mode have to switch to a supported data setting before the app will start.
The app runs on macOS, Windows, and Linux. On your phone, it works on iPhone with iOS 18 or later, iPad with iPadOS 18 or later, and Android 9 or later. The Android app is on Google Play as ai.x.grok.bot. The official walkthroughs live in the desktop getting started guide and the mobile guide.
Rundown Guides' own setup tutorial points new users toward Cursor's seven day free trial as the entry path. AI educator Debbie O'Brien, who documented her full setup on video, reported using most of that trial in two days of active testing. Treat the trial as a real limit, not a formality.
Have these ready before you start:
- An eligible Cursor plan or a linked SuperGrok subscription, plus a Cursor account for sign in
- The apps you actually want a bot working in. Gmail, GitHub, LinkedIn, Notion, Slack, Google Calendar, and the Microsoft plugins for Outlook, Calendar, and OneDrive cover most first setups
- Ten to fifteen minutes without interruptions, since the first bot walks you through a short onboarding conversation
Start with one bot, not a team
Every early setup that worked well started the same way. One bot, the premade Chief of Staff role, before anything else gets built.
That advice shows up in three separate places. Krista Letz, SpaceXAI's own enterprise go to market lead, published a playbook built around a Chief of Staff that coordinates specialists instead of working alone. Debbie O'Brien put it plainly in her video walkthrough: name one bot, let it look at your connections and your work, then ask it to design the rest of the team for you. Rundown Guides' tutorial uses the same pattern and warns against spreading a new user across many bots on day one.
The prompt that got O'Brien her clearest results asked the Chief of Staff to do three things. Review her connections. Build a profile of her workstreams and projects. Then recommend the three most useful agents, automations, and plugins to add.
Answer its follow up questions honestly. It uses your answers to decide which specialists are worth creating, not just to make conversation.
Connect your plugins, in the right order
In the desktop app, plugins live under Settings, then Plugins. You add one, approve it in your browser, and you're done. From then on, every bot on your account can use it, not just the one that installed it. Official bot templates, including the Haggle Bot procurement specialist, are in the Grok Bot marketplace.
Two connectors behaved differently in O'Brien's setup. It helps to know about them before you hit them.
GitHub can show as connected and still block you. O'Brien had GitHub linked through Cursor, and a bot treated it as available for cloud agent tasks right away. But Grok Bot's own GitHub plugin still asked her for a personal access token on top of that. If this happens to you, nothing is broken. They're two different connection paths that don't share state yet.
X doesn't use the same quick sign in flow as the rest. Gmail, Calendar, and Notion connect through a standard approval screen. O'Brien found that X asks for a developer bearer token (a key you generate in the X developer portal) before a bot can post or read for you. Budget ten minutes for that portal the first time. Or skip X for now and add it once the rest of your setup works.
For anything without a plugin, the bot hands you its cloud computer directly. A banner appears, you sign in or clear the security code prompt yourself, then you tell it you're done and it carries on. It never sees your password in that flow.
Let the Chief of Staff build the rest
Once your first bot has looked at your connections, don't name five bots yourself. The faster path is to ask the Chief of Staff to propose them, review the list, and approve what's actually useful.
In O'Brien's setup, a typical recommendation for someone juggling code, content, and outreach looked like this: a coding bot limited to specific repositories, an inbox bot for triage and drafts, and a bot for one social platform. Add a fourth only when a real task keeps getting in the way of the first three. O'Brien built seven bots of her own and still put it simply: don't add a bot for every subtask, or you're just adding another handoff to manage.
Grok Bot teams get built from the top down. One coordinating bot reviews what you've connected and proposes the specialists. You approve the ones worth creating.
Rundown Guides notes that each bot gets one conversation thread by design. That's a good reason to keep each bot focused on one role, instead of piling every task into a single thread and hoping it stays organized.
Five things that will trip you up
These surfaced across different early setups. Here they are in one list, so you don't have to find each one the hard way.
- A LinkedIn post can't be changed once it's live. O'Brien found that a bot can draft, review, and publish a post, but LinkedIn won't let you edit a published post to add an image. If you want a screenshot or graphic attached, ask the bot to add it as the first comment instead.
- Constant connector syncing costs more than it saves. Rundown Guides warns that asking bots to check and sync a connected service over and over burns through usage faster than batching updates. Saving and reporting once at the end of a work session is the pattern that held up.
- A GitHub connection through Cursor doesn't cover Grok Bot's own GitHub plugin. Don't assume one green checkmark covers both paths.
- Publishing takes longer than a normal social post. In O'Brien's setup, several minutes passed between asking the bot to post and the post appearing. That's expected, not a stall. Wait before you assume it failed and try again.
- A seven day trial goes fast under real use. O'Brien used most of hers in two days of active testing across several bots and apps. Plan your first real session with that in mind.
Three prompts to copy on your first day
These come from Bot Directory, an open prompt directory for Grok Bot where anyone can contribute a tested setup:
Chief of Staff briefing. Connect the tools you use every day. Then ask it to walk you through connecting each one and to save itself as a bot once it has what it needs.
Tracking one account. For anyone in sales or client work: a bot dedicated to one account. It watches the relevant Slack channels, digests calls and emails as they happen, and answers questions about that account from what it has learned over time.
Weekly account digest. A version of the above that runs every week. It's useful once you manage more than two or three accounts and want a standing summary instead of a single setup.
Start from one of these rather than a blank prompt. Adjusting a working setup is faster than describing what you want from scratch.
What to learn next
Setting up a small agent team raises the same questions you'd face with bigger AI systems. What should each bot be allowed to touch? What runs on its own, and what waits for you? What happens when one part fails? You don't need to be an engineer to think this way, but it helps to practice it on purpose.
Go deeper on Grok Bot:
- What Grok Bot is and how it handles your accounts
- Grok Bot news and updates
- Grok Bot use cases
- Our AI tools hub, a running guide to the assistants and agents worth your time
Want a structured path with someone to guide you? The AI program comparison shows what each 4Geeks program includes at a glance.