Grok Bot 1.0: Team Bots, Slack, Teams, meetings

Grok Bot left beta on November 11. Team Bots now work in Slack, Microsoft Teams and video calls, learn from the whole team, and Gopuff ordering is built in.

Grok Bot 1.0 in one line: Bots now work for a whole team, not one person · they join Slack, Microsoft Teams and video calls on Google Meet, Zoom and Teams · they follow up on unfinished work without being asked · teammates can teach them, with an owner approving what the whole team gets · Team Bots need a Team or Enterprise plan, and meetings need Team, Enterprise or Ultra. Gopuff grocery delivery also went live inside Grok Bot the same day.

The official Grok Bot account announced the release on X on November 11, 2026: "Introducing Grok Bot 1.0. AI teammates that work alongside your whole team." xAI's own write-up of the launch is dated November 2, and some of what it lists, such as Team Bots and better sign-ins, was already rolling out in the Grok Bot 0.78.1 update. So treat 1.0 as the point where these features came out of beta together, not as a single day when everything appeared. Below is what is actually in it, checked against xAI's documentation, and what it means if you run Bots for a team.

What changed from the beta

During the beta, a Grok Bot was mostly a personal assistant: one person, one Bot, one cloud computer. xAI describes 1.0 around three ideas. Bots are now multiplayer, so a whole team works with the same Bot and it learns how each person contributes. They are proactive, so they notice work that needs doing and offer to take it on. And they are more capable, with steadier browsing, better documents and slide decks, and improved Gmail, Google Calendar and GitHub connections.

The rest of this post takes those in turn, starting with the part most teams will notice first: sharing.

Team Bots: drafts, sharing and roles

A new Team Bot starts as a draft that only its creator can see. When it is ready, the creator selects Publish, and teammates can find it. From the Share button at the top right of a chat, you can open it to your team, your whole organization, or only people you invite, and you can add individuals or groups by name.

There are three roles. The Owner created the Bot and can change it, share it and delete it. A Manager can change how the Bot works and share it. A Collaborator can chat with it but cannot change or share it. To stop sharing, the owner chooses Only you.

Two details matter for privacy. First, each person's chats with a Team Bot are private: owners and Managers cannot read them. Second, a Team Bot link and a template link are different things. A Team Bot link opens the same shared Bot for everyone. A shared template gives each person their own copy, which is how most public Bots on GrokShelf are shared. If you want a starting point rather than a shared teammate, browse Grok templates.

Whose accounts a Team Bot uses

This is the part to read twice before you share a Bot widely. According to xAI's docs, Team Bots always run in the cloud. In your own chat with a Team Bot, it can use your connected apps, but it asks before using your personal accounts. In Slack channels, threads and group chats, it runs on a shared computer and uses only the owner's apps.

Owners and Managers can also set up shared connectors under Setup, then Service accounts, then Shared connectors. Each app can use individual accounts, share one person's account with everyone, or use a separate account for the Bot where the app supports it. Sharing a personal login is off by default: an admin has to switch on Allow Shared Logins in the Grok Bot dashboard first. When it is on, anything the Bot does through that login is done as that person.

Our advice is the same as in Using a Grok Bot safely: give a shared Bot its own account with only the access the job needs, rather than sharing a manager's inbox or admin login with the whole channel.

Learning from the whole team

A Team Bot learns from everyone who uses it, and xAI says an improvement one person teaches it can help everyone. To stop one person from changing the Bot for the whole team by accident, suggested team learnings wait under Suggested in the Bot's details until an owner or Manager approves or rejects them. What the Bot learns about you personally stays with you.

The Manage panel now has three areas: General for settings, channels and accounts, Knowledge for team learnings and skills, and Analytics, which shows messages, hours saved and top users where it is available.

Slack and Microsoft Teams

Slack already worked during the beta. Microsoft Teams is the new addition, and it needs three people to say yes. A team admin enables Microsoft Teams on the Grok Bot page of the team dashboard. The owner or a Manager publishes the Bot and selects Connect Microsoft Teams. Then a Teams administrator approves it in the Teams admin center under Teams apps, Manage apps, Pending approval. Microsoft does not notify the admin, so you have to send them the link yourself, and after approval Teams can take up to an hour to finish setting the Bot up.

Once it is in, you can mention the Bot in a channel, add it to a group chat or message it directly. The first time, it sends a card visible only to you asking you to link your Microsoft account. It acts for the person who asked, uses that person's usage allowance, and asks before risky actions. It can read files attached to posts, sends files back through your OneDrive, and moves file requests from a channel into a direct message.

Bots in meetings

Bots can now join calls on Google Meet, Zoom and Microsoft Teams. You paste the meeting link into your chat with the Bot, ask it to join and take notes, and approve the card; the host then admits it. It appears in the call with its name and the word transcribing, so everyone can see it is there. A Bot connected to your calendar can also join scheduled meetings by itself.

In the call, you address the Bot by name in the meeting chat and it answers there. xAI's documentation describes it listening, taking notes and replying in chat; it does not say the Bot speaks out loud. When the call ends, it posts a summary and action items in your chat, and you can ask for a past meeting's summary or transcript later. If you only want notes, Disable Interactivity keeps it listening without replying. It will not share your credentials with others in the meeting, and if someone asks for something it held back, it tells you who asked.

Meetings are available on Team, Enterprise and Ultra. On Enterprise, an admin has to turn them on under Bot Capabilities.

Proactive Bots

The biggest change in behaviour is that Bots now start work without being asked. xAI says they watch ongoing projects, notice when something needs attention, prepare material ahead of deadlines, follow up on unfinished tasks, coordinate with other Bots and bring in a person when a decision needs judgment. They still ask before risky actions.

This is useful and also a reason to watch your usage. Every check-in is a run, and Grok Bot allowances were reset only once this month after many users ran out. Keep an eye on Settings, then Usage & Billing, in the first week after you switch on a proactive Team Bot.

Other improvements since the beta

xAI lists more reliable browser navigation and sign ins with fewer interruptions, better documents and decks, Pages that a team can edit together or keep up to date, and better Gmail, Google Calendar and GitHub connections. Approvals are smarter too: Bots are better at recognising when an action is already authorised, so you see fewer approval prompts, while xAI says sensitive information stays protected. The company also says each task uses fewer resources, without giving a number.

Gopuff ordering inside Grok Bot

Also on November 11, the Grok Bot account announced you can now order groceries, snacks and essentials from start to finish with Gopuff, which said in its own post that it is "now built directly into Grok Bot" and "Live now.". You browse, build an order, choose how to pay and check out in the chat. Gopuff says delivery takes as little as 15 minutes, which is its own claim, and it delivers only in parts of the United States and the United Kingdom, so check your address first. It builds on the shopping and Shop Pay support in the 0.78.1 update.

What this means for teams choosing Bots

For a small team, the practical change is that one well set up Bot can now serve everyone, in the channels where work already happens. That makes the choice of Bot more important, not less. A Team Bot with broad access and a vague job is harder to trust in a busy channel than one with a single clear purpose. Start with one job, such as meeting notes, weekly reporting or incident updates; Incident Update Writer is a good example of a Bot built for a shared channel. Browse more focused picks in Top Grok Bots by job.

Security deserves a mention too. This week researchers published claims about Grok Bot's cloud sandbox that SpaceXSI has not yet answered, covered in Grok code leaks and security flaws in 2026. A Team Bot in a shared Slack channel reads whatever people post there, so the advice to give it narrow, dedicated accounts matters more, not less.

Questions people are asking

Is Grok Bot out of beta? Yes. The Grok Bot account announced version 1.0 on November 11, 2026.

Do I need a team plan? For Team Bots, Slack, Microsoft Teams, shared connectors and team learnings, yes: Team or Enterprise. Individuals still get the browser, documents and approval improvements, and Ultra subscribers get meetings.

Does the Bot talk in meetings? xAI's documentation describes it taking notes and answering in the meeting chat. It does not say the Bot speaks aloud.

Can the owner read my chats with a Team Bot? No. Each person's chats are private, according to xAI's docs.

Is Gopuff available everywhere? No. It delivers only to selected areas in the United States and the United Kingdom.