Honest fence (read first): This Grok Bot Tuesday flagship is built on SpaceXAI’s own launch post, its public Grok Bot changelog, the official @bot account on X, and one creator demo. On September 28, 2026 SpaceXAI launched Team Bots — Grok Bots “that work and learn alongside your team” — and said “Team Bots is available today in public beta on Teams and Enterprise plans.” On October 1 the @bot account posted: “Grok Bot can now suggest ways to help without you needing to ask.” On October 2 changelog v0.66.0 added: “Choose a primary Bot, marked Main Bot with a star, that checks in proactively and coordinates work with your other Bots; requires Grok Bot 0.59.0 or later.” The striking numbers in the launch post — a five-person team shipping “more than 100 PRs a day,” a customer “saving our customers over $120,000” — are SpaceXAI’s own examples and a customer quote, not audited results. No adoption or usage figures have been published for either feature. Not a re-run of the Sep 29 support-tickets post, the Sep 30 growth-comment post, or the Sep 30 $20-walkthrough post: the new facts are the Team Bots beta and the Main Bot. Embed: Riley Brown c9Z7ixVr4CU (Oct 5; chapters 00:20 Primary Bot and 07:11 Team Bot Feature).

Riley Brown — “Grok Bot Just Changed A LOT (Here’s What’s New)” (published October 5, 2026; chapters 00:20 Primary Bot and 07:11 Team Bot Feature). Feature details cite SpaceXAI’s launch post and changelog, not the YouTube title.

Editorial Thesis

For two months Grok Bot has been a personal agent: your Bots, your computer, your logins. Team Bots is the first time SpaceXAI is selling it as shared infrastructure — one Bot, one set of skills and plugins, used by a whole team in the app and in Slack — and the Main Bot is the first time the product is designed to start the conversation instead of waiting for one. Both are real, shipped, documented changes. Claim vs proof: the documentation is the receipt for what the features do; nothing yet is a receipt for how much work they save.

Honest Verdict

Believe that Team Bots and the Main Bot exist and work as described: they are in a dated launch post and a versioned changelog, and a 295K-subscriber creator walked through both on camera. Treat “more than 100 PRs a day,” “saving our customers over $120,000” and the 45,000-table Data Bot as company-selected showcases. Remember the plan gate: Team Bots is a public beta for Teams and Enterprise plans; individual plans are not listed for Team Bots. The Main Bot entry names a minimum app version (0.59.0), not a plan. Public beta means behaviour can change.

What the primary actually says

SpaceXAI — Team Bots launch post (Sep 28, 2026)

  • A Team Bot is built “around a role or workflow your team shares” and brings together four things: context (files, instructions, skills), plugins (e.g. Salesforce, Notion, GitHub), credentials for APIs without a plugin, and memories.
  • “Although the Bot is shared, each person’s conversations with it remain private.” It keeps separate context and memories per user while sharing team skills.
  • Each Team Bot gets its own Slack handle so a channel can work with it together.
  • Pre-built Team Bots for sales, product management, marketing and data analytics.
  • SpaceXAI’s own examples: a Bot per major sales account that posts a morning Slack briefing; an Engineering Bot that “steered a Cursor Project that orchestrated hundreds of Cloud Agents, helping a five-person team ship more than 100 PRs a day”; a Marketing Bot that takes approved website and SEO changes to a preview link for sign-off; a Data Bot using read-only credentials over a skills library for “more than 45,000 tables.”
  • Customer quote (Harper CEO Dakotah Rice): “We built a Team Bot in 24 hours … saving our customers over $120,000 from hundreds of policies.”

SpaceXAI — Grok Bot changelog (Sep 26 – Oct 2, 2026)

  • v0.61.0 (Sep 26): publish a Bot to your team; “Teammates’ use of a Team Bot counts against their own allowance”; “A Team Bot asks before using your connected plugins.”
  • v0.63.0 (Sep 29): in Slack, a Bot that needs approval posts a Review an action card only you can answer.
  • v0.64.0 (Sep 30): Team Bot Managers can edit profile, skills, plugins, secrets and Slack app.
  • v0.65.0 (Sep 30): voice chat with a Team Bot; Automatic Updates on by default.
  • v0.66.0 (Oct 2): the starred Main Bot that “checks in proactively and coordinates work with your other Bots.”

Grok Bot (@bot) on X — Oct 1, 2026

  • “Grok Bot can now suggest ways to help without you needing to ask.”

Creator demo — Riley Brown (Oct 5) — attributed

  • Shows the Primary Bot handing a redesign request to his dev Bot, and calling the Primary Bot hands-free from the iOS app; then the Team Bot setup, publishing and Slack use. His “pushed the change straight to prod” example is his own workflow, not a SpaceXAI claim.

Why this is today’s Grok Bot Tuesday flagship

The previous Grok Bot pieces on AI Shift News were about access, price and growth talk. This week the product itself changed shape: shared Team Bots with per-person privacy and Slack presence, and a Main Bot built to come to you first. Readers who run Grok Bot — including small teams deciding whether to move from individual plans to Teams — need the plain feature list, the plan gate and the fence on the showcase numbers.

Human review risks

  • Writing that Team Bots is available on every plan — it is a public beta on Teams and Enterprise.
  • Presenting 100 PRs/day, $120,000 or 45,000 tables as independent results.
  • Saying the Main Bot acts on its own — sources say it suggests, checks in and coordinates.
  • Mixing the Main Bot up with the older Grok Build /goal feature.
  • Treating the Riley Brown demo as SpaceXAI documentation.

Bottom Line

Believe that Team Bots and the Main Bot exist and work as described: they are in a dated launch post and a versioned changelog, and a 295K-subscriber creator walked through both on camera. Treat “more than 100 PRs a day,” “saving our customers over $120,000” and the 45,000-table Data Bot as company-selected showcases. Remember the plan gate: Team Bots is a public beta for Teams and Enterprise plans; individual plans are not listed for Team Bots. The Main Bot entry names a minimum app version (0.59.0), not a plan. Public beta means behaviour can change.

Sources