The week of October 19, 2026, delivered what may be the most consequential expansion yet of Grok Bot as a workplace agent. Release 0.75.2 introduced shareable Pages, richer GitHub and Gmail connectors, voice continuity, payment options, and cross-mode memory, while xAI outlined early enterprise deployments, restructured subscriptions, and retained Grok 4.7 as its reported API flagship.

Here is our professional analysis of that defined this week.

Grok Bot 0.75.2: Pages Become Deliverables

The Grok release notes describe Pages as live, shareable outputs for reports, memos, and dashboards. Version 0.75.2 also adds video creation from text or images, redesigned cards for approvals, files, links, and tables, synchronized pinned Library items, and keyboard shortcuts.

Pages change the output model. This is not simply another chat-format response; it is an attempt to make generated work persistent, presentable, and distributable without moving it into a separate authoring tool.

That raises an immediate governance issue. A live page can carry operational data farther than a private conversation, so production adoption needs clear ownership, review, retention, and sharing rules. The release notes report the capability, but the supplied material does not specify page-level retention periods or administrative defaults.

The same release-notes feed highlights Shop Pay and X Money options, alongside memory that carries across text chats and voice calls. Cross-mode memory could reduce repetition when users move between typed and spoken sessions, but it also increases the importance of defining which interactions may contribute to persistent context.

Enterprise evaluations should treat Pages and memory as information-lifecycle features, not interface conveniences. Approval gates and data-handling policies need to be established before generated artifacts become routine internal deliverables.

Connectors: Repository and Inbox Actions Expand

Grok’s release reporting says the GitHub connector can inspect repositories, commits, pull requests, branches, and comments. The Gmail connector gained actions involving attachments, reply-all, forwarding, and label colors.

That is a wider operating surface. Repository inspection can place source history and review discussion inside an agent workflow, while Gmail actions move the system beyond reading messages toward changing how communications are processed and distributed.

Teams also received page-sharing controls, organization restrictions, link previews, and team icons, according to the same release reporting. The organization restrictions are particularly relevant because connector reach and sharing controls must advance together. Broad data access without matching distribution boundaries would create an avoidable exposure path.

Voice reliability received practical changes as well. Calls can use earlier call history, reconnect after network drops, and restore the microphone automatically, while fixes target long-chat loading and other reliability issues.

Production workflows need least-privilege connector access, explicit approval boundaries for outbound email actions, and verification before repository-derived conclusions reach engineering decisions. Reliability improvements reduce interruption; they do not remove the need to inspect agent actions.

Enterprise Deployment: Controls Move Into View

NeoTeo reported that Elon Musk described Grok Bot as being in early deployment with selected enterprise customers, with wider deployment expected within weeks. At the time of writing, that statement is a rollout forecast, not confirmation of general availability.

The reported enterprise offering includes access, network, and audit controls. It also allows organizations to invite users who do not already hold seats, potentially separating collaboration access from the existing subscription base.

Perhaps the most consequential signal is the combination of agent capabilities and administrative controls. xAI is not positioning Grok Bot solely as an individual subscription product; it is reportedly building the control plane required for managed organizational use.

Usage reporting adds scale to that strategy. FourWeekMBA reported that SpaceX President and COO Gwynne Shotwell said Grok Bot had reached approximately 800,000 weekly paid users earlier in October, more than doubling over the previous month. That figure is reported through a secondary source and should not be treated as independently audited usage data.

Enterprise buyers should keep pilot scope aligned with confirmed controls. Early deployment is the stage for validating audit coverage, network boundaries, user provisioning, and artifact sharing—not for assuming that anticipated wider deployment resolves those requirements.

Subscriptions: Four Tiers Reset Budget Math

The official Grok account reportedly identified four plans: Plus at $8, Premium at $30, Super at $100, and Ultra at $200. Legacy SuperGrok and Heavy terms remain for continuing users, according to the supplied reporting.

The four-tier structure creates clearer price points but also introduces a migration question for existing users. Continuing legacy terms can complicate internal support when teams contain a mixture of old and new subscriptions with potentially different entitlements.

This is not yet an enterprise licensing schedule. It is a consumer-facing cost baseline that procurement teams can use to identify unmanaged subscriptions and compare them with any separately negotiated organizational offering.

Technology leaders need an inventory before standardizing a tier. Existing SuperGrok and Heavy users should be identified, while new purchases should be held against documented feature requirements rather than plan names alone.

Grok 4.7: API Baseline Holds

Available reporting identifies Grok 4.7 as xAI’s latest flagship model, accessible through the Grok API and Cursor. DevPick reports pricing beginning at $2 per million input tokens and $6 per million output tokens.

The supplied research does not identify a separate API endpoint, price revision, or deprecation announced during this week. That absence matters because application teams have no documented weekly migration event to execute.

For CTOs, the practical decision is to retain the reported Grok 4.7 pricing as the current planning baseline while avoiding assumptions about unannounced endpoints or retirement dates. Model verification, spend controls, and fallback routing remain necessary even when the API baseline is stable.

What to Watch

  • Wider enterprise deployment — Musk reportedly expects expansion within weeks, but buyers still need confirmation of availability, eligibility, and control coverage.

  • Page governance — Live Pages need evidence on retention, administrative visibility, organization restrictions, and external sharing behavior.

  • Connector permissions — GitHub inspection and Gmail actions increase the importance of granular authorization and auditable approval boundaries.

  • Cross-mode memory — Persistent context across text and voice needs clear controls for user consent, deletion, and organizational data handling.

  • Legacy subscription treatment — Continuing SuperGrok and Heavy terms could affect entitlement mapping, support, and consolidation plans.

  • API lifecycle notices — Application teams should watch for a documented endpoint change, pricing revision, or deprecation rather than inferring one from product releases.

Check back next week for the next xAI Weekly.