<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 Official access requires an eligible plan (SuperGrok Heavy, Cursor Ultra, or Cursor Premium Teams). There is no standalone Grok Bot subscription. Start at the official product surface <a href="https://x.ai/bot" https://x.ai/bot</a . Desktop and iOS are supported; Android is listed as coming soon with no firm date. Recent mobile quality of life updates include grouped notifications by Bot and easier direct use of the remote computer from the phone.</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 (SuperGrok Heavy, Cursor Ultra, or Cursor Premium Teams) and a Cursor account where relevant</li <li The apps you actually want a bot working in: Gmail, GitHub, LinkedIn, Notion, Slack, and Google Calendar 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.</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 connected and still block you.</strong O'Brien found that with her GitHub linked through Cursor, a bot treated it as available for cloud agent tasks immediately. But a second, separate GitHub connector inside Grok Bot's own plugin list still asked for a personal access token on top of that. If you hit this, it is not a broken connection, it is two different integration paths that do not share state yet.</p <p <strong X does not run on the same one click flow as the rest.</strong Where Gmail, Calendar, and Notion connect through a standard authorization screen, O'Brien found that X asks for a developer bearer token before a bot can post or read on your behalf. Budget ten minutes for the X developer portal the first time, or skip that connector until later and add it once the rest of your setup is working.</p <p For anything without a plugin, the bot hands you its cloud computer directly: a banner appears, you sign in or clear a two factor prompt yourself, then tell it you are done an