Grok Bot's entry price is $300 a month, and all 50 of your bots share one machine

Grok Bot opened to the public on August 11: persistent agents that run on cloud computers, sign into apps and sites that expose no API, and come back to the user when a decision or approval is required ^[10][1][2]. The pitch is a teammate you message like a colleague and who only pings you when something needs a yes ^[2]; the documentation is a list of constraints that determine whether that teammate is affordable, isolated, or installable at all.

Start with the bill. Access requires SuperGrok Heavy at $300 a month, Cursor Ultra at $200, or Cursor Teams Premium at $120 a seat ^[5], and InfoQ reports the beta is limited to those three subscriptions ^[3]. That is $3,600 a year per person at the top tier ^[20]. The cheapest door is 60 percent below the most expensive one ^[21], but it is a per-seat team license, so the saving scales with headcount rather than removing the floor. Sign-in runs through the Cursor account that holds the eligible plan ^[8], which is consistent with SpaceX having completed its Cursor acquisition shortly before launch, after the two companies had already worked together on model training including Grok 4.5 ^[18].

Then the machine, which is the constraint most likely to bite. An account can hold 50 Bots and group chats combined ^[12], and every Bot on that account shares one computer, with files, browser sessions, and logins offering no privacy wall between teammates ^[6]. The dev.to write-up states it plainly: one VM per person, separate Bots are not separate security boundaries, and if you sign an outbound sales Bot into Gmail, another Bot on the account can see that session ^[7]. Hold that against InfoQ's description of agents operating on dedicated cloud computers ^[1]. At the documented cap, 50 agents would share a single filesystem and a single set of live logins ^[22]. Parallelism and cross-Bot context passing are advertised features ^[4]; on one VM they are also the blast radius.

Credentials stay manual. When a Bot hits a login, the guidance is to take over the computer and type the password, passkey, 2FA code, or CAPTCHA yourself rather than putting any of it in chat ^[9]. Legacy Privacy Mode is not supported, so a data setting that allows cloud storage is mandatory ^[13]. Background routines keep running with the laptop closed ^[15], which is why the approval line matters: xAI's approvals doc keeps sending, publishing, filing, reimbursing, and production changes behind a human ^[16], and Auto Review can require approval before an external email or a production click ^[14]. The dev.to author's warning about blanket browser permissions is worth repeating: sites change their buttons, and the model will click the new one ^[14].

Installation is narrower than the marketing suggests. Desktop is macOS and Windows, there is an iPhone app, Linux desktop is missing, and Android is not in the current docs ^[11]. For anyone whose workstation is Linux, the product does not exist yet.

What to watch: whether per-Bot isolation arrives, since one VM per account is the difference between a roster and a shared login jar ^[7]; whether Linux and Android appear in the docs ^[11]; whether the $120 seat price survives the beta ^[5][3]; and whether the official roster of jobs, from Sales Outbound to Chief of Staff ^[17], produces receipts. The product was eight days old in public when that catalog was written, and its author says he has no month of production evidence ^[19].