<p <strong Setting up Grok Bot takes about ten minutes, but the order you do things in changes how useful it is by day three. This walks through the actual setup: your first bot, the plugins worth connecting first, and the specific mistakes real early users ran into before finding a working routine.</strong </p <p <em A note on scope: this covers getting a working team running, not whether you should connect it to anything sensitive. Shared sessions across bots, what happens with banking or payroll credentials, and what SpaceXAI's own documentation says about liability are covered in full in <a href="https://4geeks.com/en/blog/ai tools/what is grok bot" our companion article on what Grok Bot actually is</a . Read that first if you have not already, since the credential sharing described below is real and by design, not a bug.</em </p <p Every plugin you add, every bot you name, sticks around and works while you are doing something else. That is the point, and it is also why the order matters more than it looks like it should.</p <h2 id="before you open the app" Before you open the app</h2 <p Grok Bot is included with eligible Cursor plans (Pro, Pro+, Ultra, and Teams Standard/Premium) or by linking a SuperGrok, SuperGrok Plus, SuperGrok Heavy, or X Premium+ account. SuperGrok Lite is not included, and SuperGrok Team or Enterprise linking is not supported. There is no standalone Grok Bot subscription. Start at the official product surface <a href="https://x.ai/bot" https://x.ai/bot</a . Official step by step docs live at <a href="https://docs.x.ai/grok bot/get started" https://docs.x.ai/grok bot/get started</a (desktop) and <a href="https://docs.x.ai/grok bot/mobile" https://docs.x.ai/grok bot/mobile</a . Desktop covers macOS, Windows, and Linux. Mobile apps support iPhone (iOS 18+) and Android (Android 9+); iPad is not supported. The Android app is available on Google Play as <a href="https://play.google.com/store/apps/details?id=ai.x.grok.bot" ai.x.grok.bot</a . Sign in uses a Cursor account; accounts still on Legacy Privacy Mode must switch to a supported Cursor data setting before Grok Bot can start. Enterprise admins enable and manage organization wide access from the Cursor dashboard at <a href="https://cursor.com/dashboard/bot" https://cursor.com/dashboard/bot</a .</p <p Rundown Guides' own setup tutorial points new users toward Cursor's seven day free trial as the entry path, and AI educator Debbie O'Brien, who documented her full setup on video, reported using most of that trial window in two days of active testing. Treat the trial as a real constraint, not a formality.</p <p Have ready before you start:</p <ul <li An eligible plan or linked SuperGrok / X Premium+ account, and a Cursor account (required for sign in)</li <li The apps you actually want a bot working in: Gmail, GitHub, LinkedIn, Notion, Slack, Google Calendar, and the new Microsoft plugins for Outlook, Calendar, and OneDrive cover most first setups</li <li Ten to fifteen minutes uninterrupted, since the first bot walks you through a short onboarding conversation</li </ul <h2 id="start with one bot not a team" Start with one bot, not a team</h2 <p Every early setup that worked well started the same way: one bot, the premade Chief of Staff role, before anything else gets built.</p <p The reasoning shows up independently in three separate places. Krista Letz, SpaceXAI's own enterprise GTM lead, published a playbook centered on a Chief of Staff that orchestrates specialists rather than working alone. Debbie O'Brien, in the video walkthrough of her own setup, put it plainly: 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, built around the same pattern, calls it a focused team led by one coordinating bot, and warns against spreading a new user across many bots on day one.</p <p The prompt O'Brien used to get her clearest results asked the Chief of Staff to review her connections, build a profile of her workstreams and projects, and then recommend the three most useful agents, automations, and plugins to add.</p <p Answer its follow up questions honestly. It uses them to decide which specialists are worth creating, not just to make conversation.</p <h2 id="connect your plugins in the right order" Connect your plugins, in the right order</h2 <p Plugins live under Settings, then Plugins, in the desktop app. Add, authenticate in your browser, done, and every bot on your account can use it from then on: a connector installed once is available to every bot you create afterward, not just the one that installed it. Official Bot templates (including the Haggle Bot procurement specialist) can be added from the marketplace at <a href="https://x.ai/bot/marketplace" https://x.ai/bot/marketplace</a .</p <p Two connectors behaved differently from the rest in O'Brien's setup, and it is worth knowing before you hit them:</p <p <strong GitHub can show as already connect