When a Grok Bot feature shows up before its docs

Sometimes a new Grok Bot feature shows up in the app before any official page explains it. On September 30, 2026, that happened to us with Primary Bot. This page covers how we decided what we could honestly say, plus a checklist you can use the next time your own app shows you something new.

Botski is an independent bot built on Grok Bot. For official details, start with the official SpaceXAI Grok Bot docs.

What happened

On the evening of September 30, an Introducing Primary Bot dialog appeared in the Grok Bot app. We went looking for an explanation and didn't find one. The docs had no Primary Bot page (the address we tried returned “not found”), and there was no changelog entry, no SpaceXAI news post, and no post from the official @bot account. People on X had been posting about it since midday.

So we had a real feature on screen and nothing official to cite. We still wanted to write it up, because people were seeing the dialog and asking what it meant.

Quote the screen, word for word

The one thing we knew for sure was what the dialog said, so we started there. We took a screenshot, noted the time (about 10:43 PM CT), and copied down the text exactly: the description and both button labels, Use an existing Bot and Create Primary Bot.

We didn't fill in what the dialog left out. It doesn't say what happens to your other Bots or whether you can change your Primary Bot later, so our post says it doesn't say.

Lean on the official pages that already exist

A new feature usually builds on things that are already documented. Create and manage Bots, the Team Bots docs, and SpaceXAI’s August 11 launch post (which describes one Bot that manages the others) all helped explain the idea behind Primary Bot.

We cited them and said plainly that the idea predates the dialog. They give background. They don't confirm anything about Primary Bot itself.

Treat posts on X as chatter

Early posts are useful. They tell you when people started seeing a feature and how they use it. They aren't documentation, so we:

  • labeled every quoted post as one person’s report or opinion,
  • skipped AI-generated auto-replies, even when they sounded confident, and
  • didn't build any claim on an enthusiastic post or a skeptical one.

Say “no official docs yet,” then come back

The most useful sentence in our Primary Bot post might be the plain one: there’s no official page yet. Readers can tell exactly where the facts stop. We also said we’d update the post when an official source appears, and Scout, our docs watcher, keeps checking for one.

Checklist for the next new feature

  1. Screenshot it and write down the date and time.
  2. Quote what the screen says, word for word, buttons included.
  3. Don't guess at what the screen doesn't say.
  4. Cite the closest official pages, and say they came first.
  5. Label posts on X as chatter, and leave out AI auto-replies.
  6. Say “no official docs yet” in plain words.
  7. Come back and update when the docs land.

The short version

When a feature arrives before its docs, write down what you can see, cite what’s already official, label everything else as chatter, and say clearly what isn’t known yet.

See also

Sources

Fetched 2026-10-01 CT.

Cookie preferences