What's New in Grok Bot 1.0: Team Bots, Meeting Participation, Pricing, and What Individuals Get [2026]

Hi, Hoda here.

Grok Bot has left beta and is now Grok Bot 1.0. Here’s the conclusion up front. The core of this release is turning the Bot from a one-person AI assistant into an “AI coworker” the whole team can share and bring into Slack, Microsoft Teams, and video meetings. However, most of that is for The X Subscription’s Team (Teams) / Enterprise plans. For people using Premium or Super individually, what reaches you is mainly improvements to browser control and document creation, fewer approval prompts, and smaller UI improvements. Joining meetings is available to individuals on Ultra.

The teams that benefit most are those working in Slack or Teams where “different people ask the AI separately for the same research and the same number-crunching.” If you use it on your own, updating the app is enough, and there’s no need to rush into changing plans.

This article draws on the official announcement, the changelog, and the official documentation as of November 12, 2026 (Japan time) as primary sources, with reference to reactions on X.

What Changed in Grok Bot 1.0 (The Bottom Line)

The official announcement sums up the changes since beta in three big points (Introducing Grok Bot 1.0).

1. Multiplayer. You can share a Bot and bring it into Slack, Microsoft Teams, and video calls. It learns from the people it works with and deepens its understanding of the team’s knowledge and preferences.
2. Proactive. It notices work that needs doing and offers to take it on, follows up on unfinished work, and calls in a person when a decision is needed.
3. Stronger capabilities. Browser control is faster and more stable, and document and presentation creation have been strengthened. It also uses fewer resources for the work.

In the official framing, Grok Bot started as “a way to hand work to an AI coworker,” and 1.0 aims to understand the team’s work and the people doing it, and contribute like any other coworker.

That said, looking at what actually landed in 1.0.0 / 1.0.1 in the changelog, the specifics are these:

• Joining meetings: Joins Google Meet, Zoom, and Microsoft Teams calls via link, answers in the meeting chat, and sends a summary afterward (Team / Enterprise / Ultra)
• Microsoft Teams integration: You can add a Team Bot to Teams
• Shared connectors: Owners and Managers can share their app logins with the team (requires admin permission)
• Review learnings: What team members teach a Team Bot is held until an owner or Manager approves it
• Bot sharing: Admins can restrict who is allowed to share Bots
• Small improvements that also matter to individuals: a voice speed slider (0.5x to 2x), re-checking prices on expired order cards, no longer sending messages that just say “Done,” and so on

The “browser control improvements,” “Pages,” and “fewer approvals” emphasized in the 1.0 announcement actually arrived in sequence in v0.71 to v0.75 in October. It’s easiest to think of 1.0 as a milestone that puts a name on what accumulated during the beta.

About the Announcement Date: November 2 vs. November 11

The dates are a little confusing, so here are just the facts I could confirm.

So the announcement page itself carries a November 2 date, but the announcement on the official X account and the release of the app numbered “1.0” were on November 11 (US time). Flavio Copes’s explainer, “What’s new in Grok Bot 1.0,” points out the same thing. As of November 5 there was even a post on X saying “1.0 has been out for a few days already,” so the page may have gone live first. The circumstances of its publication aren’t explained officially, though. In this article, I treat November 11, 2026 (US time) as the official release date.

When Did the Beta Start?

The beta began on August 11, 2026 (the date on the official “Introducing Grok Bot”). At that time it was offered on desktop and iOS to SuperGrok-type, Cursor Pro / Pro+ / Ultra, and Cursor Teams subscribers. The oldest version numbers I can confirm in the changelog are v0.17.0 / v0.18.0 (both dated August 12). Some secondary sources call the version at beta launch “Beta-0.18.0,” but I couldn’t confirm that as an official designation. Team Bots first appeared in the update on September 26 (changelog).

Beta vs. 1.0 (Comparison Table)

Based on the documentation and changelog, here’s how the beta period and 1.0 differ.

In a word, the change from beta is that it isn’t just “made usable by everyone.” It’s a release that adds approval and management mechanisms so that things are less likely to go wrong when everyone uses it. Review learnings, the shared connector switches, and sharing restrictions are exactly for that.

Team Bots: Sharing One Bot Across a Team

What Is a Team Bot?

Bots come in two kinds: “personal Bots” and “Team Bots.” A Team Bot can be shared with a team, the whole organization, or specific people and groups, much like sharing a document (Team Bots documentation). Key points to know:

• Sharing doesn’t create a copy. Everyone talks to the same Bot (if you distribute it as a template, each person gets their own copy).
• Each member’s conversation is private. Even owners and Managers can’t read other people’s chats.
• Team Bots always run in the cloud. A Bot that runs on your own PC can’t be shared.
• Some screens still say “shared Bots,” but that’s the same thing as Team Bots.

Just before 1.0, the official X account introduced an example of an internal “Data Bot.” It’s a Team Bot that lets employees ask a data scientist anytime: PMs look up product usage, marketers measure campaign results, and each team uses it for building dashboards and tracking metrics (@bot post, November 2, 2026 UTC). It’s a good example for getting a feel for what Team Bots suit.

Creating and Publishing a Team Bot

A Team Bot starts as a draft and is visible only to you until you Publish.

:::steps

1. Create a Bot Choose “Create a Bot” from the ”+” in the sidebar and give it a name.

2. Tell it what it will help with You can get started by describing, in about a sentence, what it will help the team with.
3. Work through setup Set up apps (connectors), secrets, skills, and files by following the cards’ guidance. The keys and files you add here are used in the chats of everyone you share with.
4. Publish When the Bot says it’s ready to share, Publish it. Team members can then find it.

After that, each member links their own Microsoft account just once from the “Link Account” card that appears the first time they talk to the Bot. On Teams, you can use it by mentioning it in channels, adding it to group chats, and in DMs. Files are sent via the person’s own OneDrive. If you ask for a file in a channel or group chat, you’ll be told to ask again in a DM.

The documentation also collects fixes for cases where custom apps aren’t allowed in your organization or are blocked by app policies, in a troubleshooting table. For companies with an IT approval flow, this looks like the part that will take the longest during adoption.

Joining Meetings: The Bot Enters Video Calls

The part of 1.0 that matters to individual users too is joining meetings. It’s available to individuals on the Ultra plan. It’s also available on Team / Enterprise (Meetings documentation).

:::steps

1. Paste a meeting link Paste a Google Meet, Zoom, or Microsoft Teams link into your chat with the Bot and ask it to “join and take notes.”
2. Approve the card The Bot shows a confirmation card, and you approve it.
3. The host lets it in When the meeting starts, the host admits the Bot.

pros:

• One Bot can be shared across a team, so people don’t each have to re-ask for the same research or number-crunching
• Supports Microsoft Teams in addition to Slack, and can join meetings
• What the team teaches it is approval-based, so a wrong procedure is less likely to spread to everyone
• Reply usage is charged to the requester, so the cost isn’t concentrated on the owner
• Individual users still get the improvements to browser control, document creation, and approvals cons:
• The headline Team Bots, Teams integration, and shared connectors require a Team / Enterprise plan
• Joining meetings requires the $200/month Ultra plan for individuals
• Microsoft Teams integration has three approval levels and needs coordination with IT
• Depending on settings, shared connectors and Slack Workspace Access can make it unclear “whose permissions and whose allowance” apply
• “Proactive” is modest in practice, and you can’t turn off offers (check-ins) yourself
• Official documentation doesn’t state transcription accuracy for non-English meetings

If You’re Adopting It for a Team

:::steps

1. Narrow it down to one shared job Start by choosing one job where several people are asking the AI for the same thing, such as “data analysis” or “first-pass research on inquiries.”
2. Have an admin decide the sharing policy Check Bot sharing (everyone or admins only), Allow Shared Logins (keep it off by default), and Slack Workspace Access (on by default).
3. Create the Team Bot and Publish it Include only apps, secrets, and files that you’re fine with everyone you share with using.
4. Share small with “People you invite” At first, limit it to invited people and groups rather than the whole team.
5. Connect it to Slack or Microsoft Teams Teams requires three levels of approval, so talk to IT early.
6. After a week, look at Review learnings and Analytics Approve or reject the learnings the team has proposed, check how it’s being used, and then widen the scope.