Grok Bot from the first sitting: a setup checklist and the index of episodes 01 through 12

Disclosure: aitamer.news is produced with Grok Bot and Cursor, two of the products covered in this tutorial.

Episode 12 is the boundary around a computer you already have. This tutorial is the first sitting if the app is still unopened, and the index if it is not. If a click below disagrees with the app, follow the app. Episode 01 set that rule. Two official guides were both open on 22 October 2026, and they do not describe the same first screen.

Install, then sign in

The Cursor get-started page sends you to the Grok Bot page of the Cursor dashboard. Download Grok Bot installs the desktop app or copies a link. Without dashboard access, ask an admin for the link. The page lists macOS (Apple silicon and Intel), Windows (x64 and Arm64), and Linux (x64 and Arm64), and says the app checks for updates. iPhone install is the App Store, on iOS 18 or later, with the same Cursor account.

The SpaceXSI get-started page sends you to the downloads page: an Apple silicon or Intel disk image, a Windows x64 or Arm64 installer, and Linux packages under More downloads on x.ai/bot, as .deb, .rpm, or AppImage. Check for Updates is under Settings, then Updates. Phone updates on the how-to page come from the App Store or Google Play. If desktop says Update required, that page is the recovery. A reinstall from cursor.com/dashboard/bot keeps the Bots and chats, because they belong to the account.

Choose Sign in and finish in the browser. There is no separate Grok Bot login. Single sign-on is the company Cursor flow. Already inside the app, the SpaceXSI page uses Sign In with Cursor under Settings. If access is a SuperGrok subscription, link it when asked. On iPhone and Android that page shows Link Grok Account, then Finished Linking? Refresh My Status. On desktop, Settings, then Usage & Billing, offers Get Access with Grok.

The Cursor page says access comes with every paid individual Cursor plan, the Cursor Teams plan, an individual SuperGrok link, or a seat on a self-serve Grok Business plan. The SpaceXSI “before you begin” list names the same Cursor plans plus SuperGrok, SuperGrok Plus, and SuperGrok Heavy, but no Grok Business seat, so it is the shorter list. Episode 06 is the matrix. Read it before you quote a price. This checklist prints none.

Grok Bot needs cloud data storage. Privacy Mode (Legacy) prompts you to switch before the app can start, and the teams page says that setting blocks Grok Bot entirely. Episode 12 is what leaves the computer after you are in.

The first Bot, on the screen you have

The Cursor get-started page and onboarding agree on the start. Click through the intro. The app creates a Bot named Grok Bot and opens its chat. Onboarding starts another Bot at New chat, the + button, then Create new Bot. The get-started page calls that + button New Bot. Type a name first and choose Create “Name” Bot if you want the name up front. On a team, Create new Team Bot in the command palette makes the shared Bot. Leave it for episode 05 and episode 09.

Edit a Bot says personal Bots no longer have a description, and the details view no longer has a Bot settings page. Put the job in the first message and ask the Bot to remember it. Onboarding’s example:

Research one product topic at a time. Use the web and the documents I share. Summarize the main findings with source links, and ask before changing any external service. Remember this for future work.

Rename it, or add a label, from the name at the top of the chat. The phone calls the label Title (optional). One job is the point.

The SpaceXSI page still opens on Meet a future teammate. It first asks which tools you use. Those answers only change the suggestions. They do not connect the tools. Pick a suggestion, or choose Create your own, and give a short name, one job, and a description. Later Bots there start at New, then Create new Bot. If that screen is showing, fill the three fields. If the screen is a chat with a Bot already named Grok Bot, use the first message. Episode 01 recorded the same split.

One task that stops

A strong first request states the outcome, the sources, the constraint, the deliverable, and where the Bot stops. Attach a document. Onboarding’s wording:

Summarize this document in five bullets. List every date, decision, and open question in a separate section. Cite the section for each item. Do not change the source file.

Read the answer. Name any format you want again, in chat. Help will not offer a description field for it afterward. The edit-bot page says a lasting rule lives in the Bot’s memory, and its example is “From now on, ask before sending any email.” Episode 12 is why that memory line still does not press Send for you.

Connect Gmail, Calendar, Slack, or Notion from the connect card or from Connect apps when a later task needs them. Episode 04 is the plugin. Episode 11 is the draft you press. The first sitting needs neither.

On a site with no plugin, choose Take over or Open computer, enter the password or code yourself, and hand control back. The Bot does not see the password. The session stays on the shared computer, which is episode 02. Use Allow once while you learn a workflow, and Deny when the action is not what you asked for.

Save a skill after a second run matches the shape you wanted. Schedule a routine only after that. Episode 03 is the clock. Teaching by demonstration, testing routines, and updating the computer stay on desktop even after the phone is signed in.

Where each episode sits

All twelve episodes answered on aitamer.news on 22 October 2026.

1. What Grok Bot is: the desktop app, the shared computer, and the two first screens.
2. The cloud computer: the hosted disk, the browser, and the files the next Bot can see.
3. Routines: a schedule or a trigger, and a stop line, including while the laptop is shut.
4. Plugins: Slack, Gmail, Calendar, and the mail.grokbot.com connection.
5. Groups: when a second Bot earns a name, and a group of two to six.
6. Plans and usage: what the seat includes, what a link stacks with, and where usage goes.
7. A Cursor cloud agent: hand a repository job off, then read what comes back.
8. At home: inbox, calendar, and chores that need your own accounts.
9. On a team: who already has it, which admin switches change the day, and a role that stops at a review list.
10. The gallery: read a template, add a copy, and file it in a sidebar section.
11. Sending: the draft card, one Gmail mailbox, and mail.grokbot.com.
12. Privacy: what leaves the computer, the masked card, Auto-review, and the rules a chat cannot skip.

A pass you can do today

Install from the page your account shows. Sign in with Cursor. On the screen you have, give one Bot one job and ask it to remember the stop. Attach a document you may share. Send the five-bullet summary, including the line that the source file stays unchanged.

Choose Deny on a card that would send, delete, purchase, or change a service. If a card wants a password, use Take over or the secure card. Stop there. The routine, the second mailbox, and the template are later episodes, and the index names which one.

That is the desk after thirteen episodes: one computer, one job with a remembered stop, a send you press yourself, and a list to reopen when the work grows a second Bot.