Grok Bot myths: what AI summaries keep getting wrong

Ten Grok Bot claims, checked

The claims below circulate in AI-generated summaries and copied “cheat sheets” about Grok Bot, the agent app from SpaceXSI (formerly xAI). Most start from something real. Some were true at launch in August 2026 and changed with The X Subscription on October 12. We checked each one against official pages on October 18, 2026.

Pricing and plans

The $100 standalone claim is false. Cursor’s Grok Bot plans page lists no standalone Grok Bot subscription. The cheapest tier that includes it is The X Subscription Premium tier at $30 a month. Super costs $100 and Ultra $200. The $100 figure is most likely the Super tier mistaken for an entry price.

“Included in SuperGrok and Cursor plans” is outdated. During the August beta, SpaceXSI made Grok Bot available on SuperGrok, SuperGrok Plus and SuperGrok Heavy, on Cursor Pro, Pro+ and Ultra, and on Cursor Teams plans. Those plans still work for existing subscribers. But since October 12, new buyers get The X Subscription, where Grok Bot comes with Premium, Super and Ultra. It also works with linked X Premium+ and Grok Business seats. It is not included in X Plus, X Free or SuperGrok Lite. Full details are on our Grok Bot pricing page.

Usage limits: separate then, shared now

At launch, SpaceXSI said Bot usage was separate from Grok and Cursor plans, so the “own limits” claim was accurate in August. It is not accurate for The X Subscription. There, Grok Bot draws from one weekly pool shared with Cursor and the Grok apps, so long background tasks do use the same allowance as chat. On older plans, Bot usage is metered on the Cursor account. Our Grok Bot limits guide explains the pool.

Features that check out

Per-bot email

True. The October 11 changelog says Bots can claim their own email address and receive mail there. Outgoing mail needs your approval on a draft card. The @mail.grokbot.com domain and an October 9 rollout come from 9to5Mac, not from x.ai. iPhone in Canada reported that email aliases able to trigger routines arrived on October 16.

Teach by demonstration

True. With “Teach a task”, you record a browser workflow of up to 10 minutes, without a microphone, and the Bot turns it into a draft skill that you should refine and test. The docs say the feature may roll out gradually. The launch post called the result a “routine”.

Purchases with Stripe

Mostly true. Officially, Link purchase cards let you Allow or Deny a payment before it completes (August 28). Link wallet cards followed on September 1, and X Money and Stripe Link payments on October 11. The detail that each approved purchase gets a single-use virtual card, US only, comes from Crypto Briefing’s August 28 report; we did not find it stated on x.ai.

Platforms

True per the docs. The FAQ lists macOS (Apple silicon and Intel), Windows (x64 and Arm64), Linux (.deb, .rpm and AppImage), iPhone and iPad on version 18 or later, and Android 9 or later. One caveat: the Android link on x.ai/bot points to the Grok app, and the changelog has no Android-specific entries.

Group chats and approvals

Partly true. Group chats hold 2 to 6 Bots. They hand work to each other in view, you can @mention one Bot or use @everyone, and admins can switch off messaging between Bots. However, approval requests, secret and login requests, and email or Slack drafts do not appear in group chats. Those happen in one-to-one chats with each Bot. See how Grok Bot works.

Templates named “Nope” and “Kin”

We could not find either. “Nope”, described as a free-trial canceller, does not appear in official sources or the press we searched. The closest official role is Subscription Cleaner on the use-cases page: it finds subscriptions and unsubscribes the ones you approve. Free trials are not mentioned. “Kin”, described as an elderly-care Bot, turned up nowhere: not in official sources, third-party directories or press. Real listings are on our template list, and sourced examples are on Grok Bot use cases.

The ~/.grok/config.toml “blueprint”

Fabricated. Only the file path is real, and it belongs to Grok Build, SpaceXSI’s terminal coding agent. Grok Bot is a separate desktop and cloud app that you set up in its own interface.

The real Grok Build file uses tables such as [models], [mcp_servers.<name>], [tools], [toolset.bash], [toolset.web_fetch], [sandbox], [session], [cli], [ui], [permission], [features], [subagents], [memory], [skills], [plugins], [compat.cursor] and [compat.claude]. The circulating version adds things we found in neither the official settings reference nor the repo’s configuration guide:

• a [runtime] table with environment_id, max_memory_mb, cpu_cores and persistence_mode;
• a [display] table with render_engine “headless-cdp” (the real file has [ui] and render_mermaid);
• an [agent_client_protocol] table with listen_address;
• a sandbox allowed_outbound_domains key (real [sandbox] keys are profile and auto_allow_bash; the closest real setting is allowed_domains under [toolset.web_fetch]).

The commands are also wrong. The binary is “grok”. There is no “grok-cli” binary and no “grok build” subcommand, and we found no –daemonize flag, “ax-tree query”, “snapshot restore” or /var/grok/run/state.json anywhere.

For more on the marketplace itself, start with our Grok Bot marketplace guide.

Questions people ask