Grok Bot 1.0: what it means for social media marketers

SpaceXSI, the company that used to call itself xAI, released Grok Bot 1.0 in early November 2026. The x.ai announcement is dated November 2, and the company's social posts about it went out around November 11. This page covers what changed, what it means for a social media team, and where it stops.

Grok Bot 1.0 is an always-on AI agent that works from its own cloud computer and can now be shared by a whole team, brought into Slack, Microsoft Teams and video calls, and left to offer work on its own. For social media teams it is a strong research and monitoring assistant for X, but its documented X access is read-only. Publishing needs a separate tool.

What is Grok Bot 1.0?

Grok Bot is an agent with a persistent cloud computer that has a browser, a command line and a file system. Work continues while your laptop is closed, and sign-ins persist between tasks, according to the Grok Bot docs (last updated November 11, 2026).

The 1.0 release names three changes: Bots can be shared and brought into Slack, Microsoft Teams and video calls; they "recognize work that needs to be done and offer to take it on"; and they are faster and more reliable in the browser, including writing documents and building presentations.

You can use it from the desktop app on macOS, Windows or Linux, the iOS and Android apps, Slack, X Chat, or by tagging @bot on X (Grok Bot FAQ, read November 12, 2026).

Which plans include Grok Bot?

Grok Bot is included in several paid plans, and the team features need specific tiers. The FAQ says Grok Bot comes with Premium, Super and Ultra on The X Subscription, where new customers start, while "Plus and Free don't include it". It also comes with legacy paid Cursor plans, Cursor Teams and seats on self-serve Grok Business. Enterprise customers go through their account team.

The docs we read don't list prices, and plan names changed several times between August and November. Check x.ai/bot for the current price before you budget. Usage on The X Subscription comes from a weekly pool shared with Cursor and the Grok apps, and some accounts can start a 7-day usage-credit trial.

What changed in 1.0 for marketing teams?

The 1.0 release moves Grok Bot from a personal assistant to a shared teammate. Four changes matter for a social or content team.

Team Bots that learn from everyone

A Team Bot is one Bot that a whole team, or chosen people and groups, can work with. The announcement says that "when someone teaches a Bot a better way to complete a task, that improvement can benefit everyone who uses it." A Team Bot uses the apps its owner added, and asks before it uses your personal accounts (Team Bots docs).

Slack and Microsoft Teams

Team Bots can be added to Slack, where a setting called Slack Workspace Access (on by default) lets members of your Slack workspace who aren't on the Grok Bot team talk to them. Microsoft Teams needs a team admin to enable it and a Teams admin to approve each Bot.

Meetings

A Bot can join Google Meet, Zoom or Microsoft Teams calls, take notes, answer in the meeting chat and send a summary with action items when the call ends.

Work it offers without being asked

Your primary Bot can spot tasks, flag problems such as a disconnected app, and follow up on unfinished work. The initiative docs say it "offers first" and asks before risky actions.

Can Grok Bot post to X for you?

No, not through its documented X access as of November 12, 2026. The docs describe two kinds of X access, and neither lists publishing:

• Public X, built in. Bots can search posts, open a post from a link, read an account's posts and mentions, see quotes and reposts, and check trends. The docs say: "This access is read-only and doesn't sign in as you."
• The X plugin. It adds account-private data: your DMs, bookmarks, home timeline and who liked your posts. It runs on your own X developer account, which needs X API credits (troubleshooting docs).

Tagging @bot on X hands a post to your Bot as a task, but @bot "posts only the confirmation on X" and the work stays in the Grok Bot app (tag @bot docs). Tagging isn't available yet for accounts based in Australia, the UK, the EU, Iceland, Liechtenstein or Norway.

Slack works differently. The Slack app "posts as the Slack user you connected", so a Bot can post in channels that user can post in.

A Bot can drive a browser, so in theory it could click through a website. The docs say sites may block automation or require human confirmation, and that the Bot should hand those steps to you. We wouldn't build a publishing process on that.

What can a social media team do with Grok Bot today?

Grok Bot is most useful for reading, summarizing and preparing work across apps. These jobs fit what the docs describe:

1. A weekday mention digest. Ask a Bot to watch X, Reddit and news sites for mentions of your brand, product and competitors, and send a short digest. The prebuilt "Overheard" Bot in the Grok Bot marketplace does this and "never posts on your behalf" (overview).
2. Thread to brief. Reply to a busy X thread with "@bot summarize this thread and send the key points to my Slack", the example from the docs.
3. Meeting to content plan. Add a Bot to your campaign kickoff, then ask it to turn the summary and action items into a content brief and a draft post list.
4. Slack request intake. The overview describes a Bot that watches for mentions of your name, starts on the ask, "like marketing copy or a campaign brief", and sends you a draft to approve.
5. A weekly report. Turn a successful task into a routine that pulls numbers every Monday and updates an interactive Page your team can read.
6. Launch checks. The 1.0 announcement gives the example of a Bot noticing that new customer research points to a different message than the team planned, then raising it.

What it can't do on its own is put an approved post on LinkedIn, Instagram, X or TikTok at 9:00 on Tuesday. That needs a publishing tool connected to the Bot.

What brand-safety caveats should you weigh?

Grok Bot has guardrails, and a few design choices deserve a decision before you hand it your brand. Each point below comes from SpaceXSI's docs or from news coverage.

• No model picker. "Grok Bot picks the model for each task, and there is no model picker." It can use first-party or third-party models, and the choice can differ between requests (FAQ). Tone can vary, so keep brand rules in writing where the Bot reads them.
• Shared learning. A Team Bot learns from everyone it works with. A good correction helps the team, and a bad instruction spreads the same way. Ask the Bot "What do you remember about me?" and correct it.
• One computer per user. All Bots on an account share browser sessions, files and command-line credentials. The docs say the separate screens "are separate work surfaces, not separate security boundaries." Don't sign in to a brand account there unless every Bot should use it.
• Share links expose configuration. A shared Bot template carries its setup, so strip secrets before you publish one.
• Approvals can expire. An approval raised by a routine expires after about 30 minutes and the action doesn't run. Turn on notifications for Bots that run routines.
• Grok's public record. In July 2025 xAI apologized after the Grok account on X posted antisemitic content, blaming a code update that was live for about 16 hours (NBC News). On January 12, 2026, the UK regulator Ofcom opened a formal investigation into X over sexualized images made with Grok (The Register). Grok Bot is a separate product, but your legal or brand team may ask about it, so have an answer ready.

The FAQ recommends "narrow Ask first rules for actions such as sending, publishing, deleting, purchasing". Add those, and keep a second approval step in the tool that actually publishes. Our approval workflow guide for AI agents shows one way to set that up.

How do you pair Grok Bot with a scheduler?

Add the scheduler as a custom MCP connector. The computer and apps docs say "a Bot can also add an MCP server that isn't in the catalog, by URL", and describe Add a custom connector at the bottom of Connect apps in the desktop app. A Remote HTTPS connector takes a server URL, optional HTTP headers and an optional OAuth client ID. If your team's MCP policy blocks the server, it can't be saved.

With a social media MCP server connected, the work splits cleanly:

Tracee is one option: its remote MCP server at https://traceeai.com/mcp lets an agent draft, schedule and publish to 13 networks, and agent posts wait in an Approvals queue by default. Tracee isn't in the Grok Bot catalog and has no partnership with SpaceXSI; you add it yourself with the documented custom connector feature. The step-by-step setup is in our guide to connecting Grok Bot to Tracee's MCP server. If you are new to the idea, start with what an MCP server for social media is.

How does Grok Bot compare with the other new agents?

Grok Bot is one of four always-on agents released this fall, alongside OpenAI Dots, Meta Muse and Claude Duet. It is the one with the clearest documented path for custom MCP servers, and the only one built into X. Our comparison of Dots, Muse, Duet and Grok Bot covers plans, connectors and privacy side by side.

Next step

If your team already lives on X and in Slack, try Grok Bot for monitoring and drafting first, with Ask first rules on anything that sends or publishes. When you want those drafts on a calendar with a person approving each one, connect a scheduler such as Tracee as a custom connector and keep the publish step there.