> ## Content Index
> Fetch the complete content index at: https://signal-engine.ghost.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Grok Bot 1.0: shared AI teammates, meeting calls and a usage-limit row. What changed and what users said
- URL: https://signal-engine.ghost.io/grok-bot-1-0-team-bots-meetings-usage-limits/
- Published: 2026-11-16T11:43:20.000Z
- Updated: 2026-11-16T11:43:20.000Z
- Description: SpaceXSI released Grok Bot 1.0 with shared Team Bots, Slack and Teams support, and Bots that join video calls. It came after complaints that plans ran out too fast, a weekly-limit reset and efficiency fixes. Here is what changed, what users said, and what it means for business.
- Author: John Caraher
- Tags: Issue 2, Trending Now, AI, Big Tech, Small Business, #Import 2026-11-16 11:45

Updated 16 Nov 2026, 13:43 SAST

**The short version:** SpaceXSI, the SpaceX artificial intelligence (AI) business behind Grok, has released version 1.0 of Grok Bot, its always-on AI agent. The company calls 1.0 "a major update to our AI teammates"[\[1\]](#cite-note-1). The main changes are shared "Team Bots" that a whole team can work with, Bots that work inside Slack and Microsoft Teams, Bots that can join Google Meet, Zoom and Microsoft Teams calls, and Bots that offer to take on work before they are asked[\[1\]](#cite-note-1)[\[2\]](#cite-note-2). The official Grok Bot account announced 1.0 on X on 11 November[\[3\]](#cite-note-3). The launch followed two weeks of public complaints that paid plans were running out much faster than before. Elon Musk, whose company SpaceX acquired xAI, the original maker of Grok, earlier this year[\[16\]](#cite-note-16), said the cost of serving Grok Bot had been "unsustainably high relative to revenue"[\[8\]](#cite-note-8). The company reset weekly limits for all users on 9 November[\[7\]](#cite-note-7) and, on 13 November, an engineer said new optimisations should give "\~7% more usage" from a plan[\[10\]](#cite-note-10). Our [analysis](#why-it-matters-for-your-business-analysis) on what this means for a business follows the news.

Contents

1. [What Grok Bot is](#what-grok-bot-is)
2. [What version 1.0 adds](#what-1-0-adds)  
  1. [Team Bots: one Bot for the whole team](#team-bots)
  2. [Slack and Microsoft Teams](#slack-and-teams)
  3. [Joining video calls](#meetings)
  4. [Offering to do work before it is asked](#proactive)
  5. [Faster and more capable, the company says](#capability)
  6. [Smaller changes in the same release](#smaller-changes)
  7. [When it was released](#release-date)
3. [The usage row behind the launch](#the-usage-row)  
  1. [The company's response](#the-response)
4. [The weekly walkthroughs](#matt-palmer)
5. [Musk's promotion](#musk-promotion)
6. [What we could not verify](#what-we-could-not-verify)
7. [Why it matters for your business (analysis)](#why-it-matters-for-your-business-analysis)  
  1. [Budget for usage, not just the subscription](#budget-for-usage)
  2. [Shared Bots need an owner](#shared-bots)
  3. [Meeting bots and POPIA](#meetings-and-popia)
  4. [Compare before you commit](#compare-before-you-commit)
  5. [What to watch](#what-to-watch)
8. [Sources](#sources)

## What Grok Bot is

Grok Bot is an AI agent rather than a chatbot. SpaceXSI introduced it in August as "your team of always-on agents" that "have their own computer, work inside tools and apps like you do, and keep working 24/7"[\[16\]](#cite-note-16). In practice that means a Bot can browse websites, read and draft email, work in connected apps and run scheduled jobs on a cloud computer of its own, asking its user for approval before sensitive steps.

The product sits in a crowded field. OpenAI launched its own always-on agents, called dots, in September[\[18\]](#cite-note-18), and Anthropic opened a research preview of a proactive agent called Claude Duet in October[\[19\]](#cite-note-19). In the space of a few months, all three of the best-known AI companies have moved from chat windows toward software that works in the background.

## What version 1.0 adds

SpaceXSI's announcement groups the changes under three headings: "Multiplayer teammates", "Proactive teammates" and "More capable teammates"[\[1\]](#cite-note-1). It says that "Grok Bot began as a way to hand off work to an AI teammate. With 1.0, those teammates understand the work your team is doing and the people doing it, so they can contribute like any other colleague"[\[1\]](#cite-note-1).

### Team Bots: one Bot for the whole team

With Team Bots, "everyone on a team can work with the same AI teammate", and a Bot can be shared with specific people or groups[\[1\]](#cite-note-1). The company says a Bot "learns individual preferences, remembers decisions, and draws on the expertise of different team members", and that "when someone teaches a Bot a better way to complete a task, that improvement can benefit everyone who uses it"[\[1\]](#cite-note-1).

That shared learning comes with a control. The official changelog says "what teammates teach a Team Bot waits under Review learnings until the owner or a Manager approves it"[\[2\]](#cite-note-2). Team admins can also restrict who is allowed to share Bots[\[2\]](#cite-note-2). Owners and Managers can share their own login to an app as a "shared connector", but only once a team admin turns on a setting called Allow Shared Logins[\[2\]](#cite-note-2). Team Bots are available on Team and Enterprise plans[\[1\]](#cite-note-1).

### Slack and Microsoft Teams

Bots can now be brought into Slack and Microsoft Teams conversations, where SpaceXSI says they "follow discussions involving multiple people, understand who's involved, and contribute relevant information or offer to pick up work"[\[1\]](#cite-note-1). Connecting a Team Bot to Microsoft Teams takes three approvals: "a team admin turns it on, an owner or Manager connects the Bot, and a Teams admin approves it", according to the changelog[\[2\]](#cite-note-2).

### Joining video calls

The changelog says that "on Team, Enterprise, and Ultra plans, a Bot can join a Google Meet, Zoom, or Microsoft Teams call from a link, answer in the meeting chat, and send a summary afterward"[\[2\]](#cite-note-2). The Grok Bot account highlighted the feature on X on 13 November: "Grok Bot can now join meetings. Ask it questions, assign it work, or have it keep track of what your team decides"[\[4\]](#cite-note-4). Enterprise admins have to turn Meetings on in settings[\[1\]](#cite-note-1). Japanese tech outlet ORIENS, summarising the official documentation, reported that the meeting organiser has to admit the Bot when the call starts, and that the Bot does not share a user's login details even if asked during a meeting[\[13\]](#cite-note-13).

### Offering to do work before it is asked

The second theme is initiative. SpaceXSI says a Bot "can monitor ongoing projects, recognize when something needs attention, and suggest next steps"[\[1\]](#cite-note-1). Its example is a Bot helping with a product launch that notices a deadline approaching and prepares the materials the team needs[\[1\]](#cite-note-1). To keep this in check, the company says Bots "respect each person's permissions, ask before taking sensitive actions, and check whether information is appropriate to share in a public channel"[\[1\]](#cite-note-1).

### Faster and more capable, the company says

Among other changes since the beta, SpaceXSI lists better browser use, stronger documents and slide decks, interactive "Pages" that can be edited together or kept updated, improved connections to Gmail, Google Calendar and GitHub, and "smarter approvals" that reduce unnecessary interruptions[\[1\]](#cite-note-1). The company also says it has "made them more efficient, reducing the resources required to complete tasks"[\[1\]](#cite-note-1). These are the company's own descriptions; we have not seen independent tests.

### Smaller changes in the same release

The changelog entry for 11 November, labelled v1.0.1, lists smaller additions too: a speed slider for a Bot's voice from 0.5x to 2x, a "Check price again" button on expired order cards, and fixes including that "files up to 250 MB on the Bot's computer no longer make a reply fail"[\[2\]](#cite-note-2). Separately, the Grok Bot account said on X that Bots can now join personal or company networks on Tailscale, a private-networking service, to reach internal tools securely[\[6\]](#cite-note-6), and that Grok Bot on Mac "can now use Messages, Mail, Notes, Reminders, Calendar, Location, and Contacts"[\[5\]](#cite-note-5).

### When it was released

The dates are slightly confusing. SpaceXSI's news page lists "Introducing Grok Bot 1.0" under 2 November[\[16\]](#cite-note-16)[\[1\]](#cite-note-1). The official changelog dates the v1.0.1 entry 11 November and says it "also includes 1.0.0"[\[2\]](#cite-note-2). The public announcement from the Grok Bot account on X came on 11 November at 20:22 SAST[\[3\]](#cite-note-3). ORIENS noted the same discrepancy[\[13\]](#cite-note-13). We use 11 November as the date most users would have seen the release.

## The usage row behind the launch

The release came at the end of a difficult fortnight for subscribers. On 1 November, an X account called Doge Norway asked Musk: "Any chance for a Grok Bot reset, @elonmusk? Lots of people say their usage ran out really fast this week"[\[17\]](#cite-note-17). Musk replied that night: "The cost of serving Grok Bot was unsustainably high relative to revenue"[\[8\]](#cite-note-8).

Complaints continued. TeslaNorth, a Canadian tech news site, reported that in a thread on 8 November (US time), subscriber Derek Neighbors told Musk that his US$200 plan had previously lasted seven days under heavy use but was now used up after 14 hours of moderate use, and that other users reported usage meters jumping to 100% mid-week[\[12\]](#cite-note-12). We have not independently checked those individual accounts.

### The company's response

SpaceXSI and Musk responded in public, in several steps:

- In the early hours of 9 November (SAST), Musk posted: "Just did a round table review with the Grok @Bot engineering team. Fixes are being implemented overnight and you should notice a dramatic improvement by tomorrow. If not, reply to this post and we will address any remaining issues right away"[\[9\]](#cite-note-9).
- On the evening of 9 November, the Grok Bot account posted: "We've reset weekly limits for all Grok Bot users"[\[7\]](#cite-note-7).
- On 13 November, Sam Sokolin, who works on Grok Bot, posted: "Shipped a few Grok Bot harness optimizations this week. You should get \~7% more usage out of your plan, and up to \~15% more on routine runs!"[\[10\]](#cite-note-10). The harness is the software that coordinates how the Bot carries out tasks[\[12\]](#cite-note-12).
- On 14 November, Musk posted "Improvements to Grok @Bot efficiency" with a link[\[11\]](#cite-note-11), which TeslaNorth reported as Musk highlighting the changes[\[12\]](#cite-note-12).

TeslaNorth also reported that Marco d'Amore, from the Grok Bot team, said the company had heard feedback about usage limits and model routing, with further harness and routine improvements planned[\[12\]](#cite-note-12). We were not able to find that post directly, so we report it as TeslaNorth's account. The changelog shows smaller fixes in the same period, including a 5 November note that "the usage chart shows the same usage as the meter"[\[2\]](#cite-note-2).

Orbital Downlink did not contact SpaceXSI for this article. The company's public statements are quoted above.

## The weekly walkthroughs

Many users follow Grok Bot changes through Matt Palmer, a SpaceXSI employee who posts "What's New in Grok Bot" videos. TeslaNorth reported that on 2 November Palmer walked through nine upgrades, led by shopping cards, payments stored in the Bot's Vault, and Team Bot logins shared by managers, and that Musk quote-posted the video[\[15\]](#cite-note-15). The official changelog for late October records shopping cards and Vault payments[\[2\]](#cite-note-2). Social media posts attribute a 1.0 walkthrough to Palmer over the weekend of 14 and 15 November; we have not watched it and do not quote it here.

## Musk's promotion

Since the launch, Musk has posted about Grok Bot almost daily, with messages such as "Hire Grok @Bot as a colleague and give it your hardest tasks!" on 11 November[\[14\]](#cite-note-14). His posts reach a very large audience; X's own counter showed more than 51 million views on that one post when we checked. That promotion is part of the story, but it is not evidence of how well the product works, and we have not treated it as such.

## What we could not verify

- Individual users' accounts of how quickly their plans ran out, including Derek Neighbors' figures, are as reported by TeslaNorth[\[12\]](#cite-note-12).
- The reported comments by Marco d'Amore come from TeslaNorth; we did not find the original post[\[12\]](#cite-note-12).
- The \~7% and \~15% usage gains are the company's own estimates[\[10\]](#cite-note-10). We have not seen independent measurements.
- Details of how Bots join meetings, beyond the changelog, come from ORIENS's summary of the official documentation[\[13\]](#cite-note-13).

## Why it matters for your business (analysis)

Analysis This section is analysis by Orbital Downlink, not news. It draws on the reporting above but reflects our own reading of it. It is not financial or investment advice.

Grok Bot 1.0 and the usage row are two sides of the same story. Agents that work in the background, join meetings and take on tasks unprompted use far more computing power than a chat window. Somebody has to pay for that. Musk's own comment that serving the product had cost more than it earned[\[8\]](#cite-note-8) is a plain statement of the economics behind every always-on agent, not only this one.

### Budget for usage, not just the subscription

For a small business, the lesson from the past fortnight is to treat agent plans like a utility, not a flat fee. Usage-based limits can change, and a plan that covered a week of work can cover much less if the provider changes how work is measured. Watch your usage meter for the first few weeks, find out which tasks use the most, and keep scheduled jobs to the ones that earn their keep. A plan that runs out mid-week can stall work you have come to rely on.

### Shared Bots need an owner

The Review learnings control[\[2\]](#cite-note-2) is the most important feature for a team. A shared Bot that learns from everyone could also learn a bad habit from one person. Decide who approves what the Bot learns, and who is allowed to share Bots and logins. If staff share an app login through a Bot, record which login it is and who can use it, and remove it when people leave.

### Meeting bots and POPIA

Bots that join Zoom, Teams or Meet calls[\[2\]](#cite-note-2) record what customers and suppliers say. South Africa's Protection of Personal Information Act applies to that information. Tell people on the call that a Bot is present, keep the notes somewhere you control, and agree how long you keep them. The same applies to Claude Meetings and to any other note-taking assistant.

### Compare before you commit

Grok Bot, OpenAI's dots and Anthropic's Claude Duet are converging on similar ideas. None has a long track record. If you are choosing one for your business, give each the same three real tasks, compare the results and the cost, and keep your data in formats you can move if you switch.

### What to watch

Watch whether usage complaints ease after the efficiency changes, whether SpaceXSI publishes clearer usage figures per plan, and whether the 1.0 features reach all plans. The pace of updates, with changelog entries on most working days in early November[\[2\]](#cite-note-2), means features can change quickly, so check the changelog before relying on a specific one.

*Disclosure: Orbital Downlink's publisher uses AI tools, including Grok Bot and Claude, in running this site.*

## Sources

1. [↩a](#cite-ref-1-a) [↩b](#cite-ref-1-b) [↩c](#cite-ref-1-c) [↩d](#cite-ref-1-d) [↩e](#cite-ref-1-e) [↩f](#cite-ref-1-f) [↩g](#cite-ref-1-g) [↩h](#cite-ref-1-h) [↩i](#cite-ref-1-i) [↩j](#cite-ref-1-j) [↩k](#cite-ref-1-k) [↩l](#cite-ref-1-l) [↩m](#cite-ref-1-m) [↩n](#cite-ref-1-n) [↩o](#cite-ref-1-o) SpaceXSI, [“Introducing Grok Bot 1.0”](https://x.ai/news/grok-bot-1-0?ref=signal-engine.ghost.io), listed under 2 November 2026 on the SpaceXSI news page.
2. [↩a](#cite-ref-2-a) [↩b](#cite-ref-2-b) [↩c](#cite-ref-2-c) [↩d](#cite-ref-2-d) [↩e](#cite-ref-2-e) [↩f](#cite-ref-2-f) [↩g](#cite-ref-2-g) [↩h](#cite-ref-2-h) [↩i](#cite-ref-2-i) [↩j](#cite-ref-2-j) [↩k](#cite-ref-2-k) [↩l](#cite-ref-2-l) [↩m](#cite-ref-2-m) SpaceXSI, [“Grok Bot Changelog”](https://x.ai/changelog/bot?ref=signal-engine.ghost.io), entries from 3 to 11 November 2026 (latest v1.0.1, 11 November).
3. [↩a](#cite-ref-3-a) [↩b](#cite-ref-3-b) Grok Bot (@bot) on X, [“Introducing Grok Bot 1.0”](https://x.com/bot/status/2120582957782200586?ref=signal-engine.ghost.io), 11 November 2026.
4. [↩a](#cite-ref-4-a) Grok Bot (@bot) on X, [post on Bots joining meetings](https://x.com/bot/status/2121320089920430181?ref=signal-engine.ghost.io), 13 November 2026.
5. [↩a](#cite-ref-5-a) Grok Bot (@bot) on X, [post on Mac apps](https://x.com/bot/status/2120946968403095906?ref=signal-engine.ghost.io), 12 November 2026.
6. [↩a](#cite-ref-6-a) Grok Bot (@bot) on X, [post on Tailscale networks](https://x.com/bot/status/2120279511707386263?ref=signal-engine.ghost.io), 11 November 2026 (SAST).
7. [↩a](#cite-ref-7-a) [↩b](#cite-ref-7-b) Grok Bot (@bot) on X, [“We've reset weekly limits for all Grok Bot users”](https://x.com/bot/status/2119871982946971659?ref=signal-engine.ghost.io), 9 November 2026.
8. [↩a](#cite-ref-8-a) [↩b](#cite-ref-8-b) [↩c](#cite-ref-8-c) Elon Musk (@elonmusk) on X, [reply on the cost of serving Grok Bot](https://x.com/elonmusk/status/2116992258520064397?ref=signal-engine.ghost.io), 1 November 2026.
9. [↩a](#cite-ref-9-a) Elon Musk (@elonmusk) on X, [post on the round table review and overnight fixes](https://x.com/elonmusk/status/2119617455102333206?ref=signal-engine.ghost.io), 9 November 2026 (SAST).
10. [↩a](#cite-ref-10-a) [↩b](#cite-ref-10-b) [↩c](#cite-ref-10-c) Sam Sokolin (@SamSokolin) on X, [post on harness optimisations](https://x.com/SamSokolin/status/2121303079803089179?ref=signal-engine.ghost.io), 13 November 2026.
11. [↩a](#cite-ref-11-a) Elon Musk (@elonmusk) on X, [“Improvements to Grok @Bot efficiency”](https://x.com/elonmusk/status/2121628295234023654?ref=signal-engine.ghost.io), 14 November 2026.
12. [↩a](#cite-ref-12-a) [↩b](#cite-ref-12-b) [↩c](#cite-ref-12-c) [↩d](#cite-ref-12-d) [↩e](#cite-ref-12-e) [↩f](#cite-ref-12-f) TeslaNorth (Sarah Lee-Jones), [“Grok Bot Gets Up to 15% More Usage After Subscriber Complaints”](https://teslanorth.com/2026/11/14/grok-bot-efficiency-more-usage/?ref=signal-engine.ghost.io), 14 November 2026.
13. [↩a](#cite-ref-13-a) [↩b](#cite-ref-13-b) [↩c](#cite-ref-13-c) ORIENS, [“'Grok Bot 1.0' released, letting teams share the same bot”](https://ai-oriens.com/en/news/grok-bot-1-0/?ref=signal-engine.ghost.io), 12 November 2026.
14. [↩a](#cite-ref-14-a) Elon Musk (@elonmusk) on X, [“Hire Grok @Bot as a colleague”](https://x.com/elonmusk/status/2120584535423565889?ref=signal-engine.ghost.io), 11 November 2026.
15. [↩a](#cite-ref-15-a) TeslaNorth, [“Grok Bot Update Adds Shopping, Payments and Team Bots in 9 Upgrades”](https://teslanorth.com/2026/11/02/grok-bot-9-upgrades-shopping/?ref=signal-engine.ghost.io), 2 November 2026.
16. [↩a](#cite-ref-16-a) [↩b](#cite-ref-16-b) [↩c](#cite-ref-16-c) SpaceXSI, [“News”](https://x.ai/news?ref=signal-engine.ghost.io) index page, including “Introducing Grok Bot” (August 2026).
17. [↩a](#cite-ref-17-a) Doge Norway (@DogecoinNorway) on X, [question to Elon Musk about a usage reset](https://x.com/DogecoinNorway/status/2116986414110007446?ref=signal-engine.ghost.io), 1 November 2026.
18. [↩a](#cite-ref-18-a) SiliconANGLE, [“OpenAI launches Dots, always-on AI agents in ChatGPT with their own cloud computers”](https://siliconangle.com/2026/09/29/openai-launches-dots-always-on-ai-agents-in-chatgpt-with-their-own-cloud-computers/?ref=signal-engine.ghost.io), 29 September 2026.
19. [↩a](#cite-ref-19-a) Claude by Anthropic, [“Introducing Claude Duet”](https://claude.com/resources/articles/claude-duet?ref=signal-engine.ghost.io), 23 October 2026.

This article is for information only and is not financial or investment advice.

Spotted an error? Tell us and we'll correct it.