Dated notes from official public Grok Bot pages, plus occasional Botski observations. This is not the email updates list.
Official public pages last checked 2026-09-20. File dates are the bylines printed on those pages. This is not an xAI release feed.
Newest first. Official means the note cites a dated public xAI page. A Botski observation is a Botski note, not an xAI release.
What changed
Official
What changed
Official guide “Grok Bot 101” published on x.ai/bot/guides. Documents standing up a Bot (name/title/description), connectors/plugins/skills, chat vs routines/triggers vs Bot-to-Bot, shared-computer permissions / Auto Review–style allow-deny rules, and multi-bot chains.
Who it affects
Anyone setting up a first Grok Bot.
What to do next
Read the official Grok Bot 101 guide when you set up your first bot. Official product docs stay at docs.x.ai/grok-bot.
Official guide “Grok Bot for Engineering” published. Documents using specialist engineer Bots to create/monitor Cursor cloud agents, close visual/CI feedback loops, private workers for VPN/special machines, and routine-driven fleet ops (nightly audits, urgency checks).
Who it affects
Engineers and teams pairing Grok Bot with Cursor cloud agents.
What to do next
Read the official engineering guide if you use Grok Bot with Cursor cloud agents. Treat shipping stories as examples, not guarantees.
Official guide “Grok Bot for Support” published on x.ai/bot/guides. Documents using a support Bot with connectors, five example jobs (release tracking, bug reproduction, churn analysis, refunds that wait for approval, and custom reporting), and turning those workflows into routines that keep running after you close the laptop. Numbers and details in the guide are illustrative.
Who it affects
Support teams setting up a first Grok Bot for a ticket queue.
What to do next
Read the official support guide when you give a Bot a support job. Treat the five jobs as examples, not a required setup. Official product docs stay at docs.x.ai/grok-bot.
Official guide “Templates for Grok Bot” published. Documents Share as Template — recipe not clone; packages skills/memories/plugins (not secrets/custom code/MCP); Public vs Team publish; Add to Grok Bot install flow and reinstall plugins after add.
Who it affects
Anyone sharing or installing a Bot template.
What to do next
If you share or install a template, read the official template guide and the third-party bot terms first.
Official guide “Grok Bot for mobile app development” published. Documents a six-Bot studio example (orchestrator, analytics, creatives, engineer, infra, and bug-fix), job descriptions, connections, routines, recorded skills, and Bot-to-Bot handoffs. Shipping results in the guide are the author’s examples.
Who it affects
People using Grok Bot on mobile build, live-ops, or multi-Bot handoff work.
What to do next
Read the official mobile-development guide if you are staffing specialized Bots. Treat download counts and ROI stories as examples, not guarantees.
Official guide “Designing Grok Bot with Grok Bot” published. Documents a designer’s always-on design agents (experiments, motion, Figma production, and engineering questions), working from real production assets, and keeping human judgment in the loop. The guide states this does not replace existing design tools.
Who it affects
Designers exploring Grok Bot for production-adjacent design work.
What to do next
Read the official design guide if you want Grok Bot to explore ideas while you keep the judgment. Official product docs stay at docs.x.ai/grok-bot.
Official guide “Grok Bot for GTM” published. Documents an Enterprise GTM setup: Chief of Staff, meeting prep, prospecting, per-account experts, data, product questions, forecasting, slides, and a sales coach, plus skills such as recording a task and feeding writing samples.
Who it affects
GTM and sales teams standing up specialized Grok Bots.
What to do next
Read the official GTM guide when you assign Grok Bot sales or account work. Official product docs stay at docs.x.ai/grok-bot.
Official guide “Grok Bot for PMs” published. Documents PM use: an attention list from Slack, email, and meetings; research across customer context; shipping via cloud agents; and a named team (Chief of Staff, eng manager, engineers, data, PM sidekick) with human review on sends, spends, and deletes.
Who it affects
Product managers trying Grok Bot as a specialized agent team.
What to do next
Read the official PM guide if you want Grok Bot to hold an attention list or help ship. Keep human review on sends, spends, and destructive actions. Official product docs stay at docs.x.ai/grok-bot.