Grok Bot 1.0 Leaves Beta as a Shared Teammate That Joins Calls

SpaceXSI took Grok Bot out of beta on Wednesday, Nov. 11, shipping version 1.0 as a set of AI agents that no longer serve one person but work inside a team's Slack channels, Microsoft Teams chats and video calls.

The release reframes the product. Shared Team Bots and Slack support arrived in September, according to the company. What version 1.0 adds is Microsoft Teams, meetings, and Bots that act without being asked. SpaceXSI's launch post calls 1.0 a major update to its "AI teammates," and the Grok Bot account on X pitches them as teammates "that work alongside your whole team."

The stakes are straightforward: the update moves Grok Bot from the crowded personal-assistant category into the contested market for AI agents embedded in workplace software, where initiative — machines volunteering for work rather than waiting for prompts — is the dividing line between a chatbot and a colleague.

What can Grok Bot 1.0 actually do?

The headline capability is meetings. A Bot can now join a Google Meet, Zoom or Microsoft Teams call from a link, answer in the meeting chat and send a summary afterward, according to the xAI changelog.

Availability splits by plan:

• Team Bots run on Team and Enterprise plans.
• Meetings run on Team, Enterprise and Ultra plans.
• Enterprise administrators must switch meetings on before teams can use them.

The larger shift, in SpaceXSI's telling, is initiative. The company says Bots can recognize work that needs doing and offer to take it on, follow up on unfinished tasks and "bring people in when a decision requires their judgment."

A Bot also learns across a team rather than for a single user. SpaceXSI says a Bot learns more about a team's work as more people use it, and something one person teaches a Team Bot can benefit everyone who uses it.

How the launch demo imagines the workday

The launch video stages the pitch around a fictional headphone launch, and it shows the behaviors SpaceXSI wants buyers to picture.

A Launch Bot posts at 7 a.m. that the product ships in two weeks and that it has created a channel to keep everyone on track. A user asks a Bot to join a call at 10, and it answers, "Of course." A Research Bot is then admitted to a video call with three colleagues, where it summarizes feedback from 80 testers, reports that "Testers love how light the headphones are" and asks, "Want me to ping marketing?"

The chain continues on its own. The Research Bot tags a Copy Bot, which replies "I'm on it" and rewrites an ad headline inside a design tool — from "Sound, reimagined." to "A lighter fit for longer days," across two ad sizes.

Later in the demo, asked to share a deck with an ad agency, a Deck Bot warns that slide 6 holds sensitive financials and offers to send a version without it. "good catch, yes," the user replies. The exchange mirrors the safeguards SpaceXSI describes in its documentation: Bots "respect each person's permissions" and "ask before taking sensitive actions."

What else changed in 1.0?

Beyond meetings and initiative, SpaceXSI credits the release with performance gains:

• Bots are faster at browser work.
• They are better at writing documents and building slide decks.
• They can create interactive Pages that teammates edit together.
• They use fewer resources per task.

The launch post gives no figures for the efficiency gain, so the resource claim rests on the company's assertion.

Who controls what a Bot can do?

Administrators hold the controls, and the permission model is layered.

Connecting a Bot to Microsoft Teams requires three separate approvals: a team admin turns the integration on, an owner or manager connects the Bot, and a Teams admin approves it.

Knowledge transfer is gated too. What teammates teach a Team Bot waits for an owner's or manager's approval before it takes effect, and admins can limit who shares Bots at all.

Those settings carry the practical weight of the release. How much unprompted work companies let Bots take on will turn on administrator configuration, and version 1.0 is the first release that puts that question to whole teams at once — not to individual users deciding for themselves.

Why the 'teammate' framing matters

The move from personal assistant to shared teammate is a structural change, not just a marketing one. A Bot that belongs to a team accumulates institutional knowledge — the sort one colleague teaches and everyone reuses — and inserts itself into group channels, chats and live calls where work already happens.

That positioning places Grok Bot in direct competition with enterprise AI agents from the major workplace platforms themselves, since Slack and Microsoft Teams are the surfaces it now occupies.

It also raises the governance question the demo only partially answers. A Deck Bot that flags sensitive financials and asks permission illustrates the intended behavior; whether real deployments match the demo depends on the admin controls the company has built and on how much autonomy enterprises are willing to grant software that volunteers for tasks.

Version 1.0 ships those controls, the meetings integration and the initiative behaviors together, and the November release makes team-shared, meeting-capable, self-starting Bots generally available for the first time.