SpaceXAI has expanded Grok Bot availability across subscription plans.
SpaceXAI has widened access to its cloud-based work assistant, while weekly usage limits and approval requirements remain.
SpaceXAI has expanded Grok Bot access to SuperGrok, Cursor Pro and all Cursor Teams plans. The move brings its cloud-based work assistant to cheaper subscriptions while retaining access on higher-priced tiers.
X Premium+ subscribers can also connect their accounts to use the service. Meanwhile, Grok and Cursor Enterprise customers can access the assistant through their organisations.
The product remains in beta and handles tasks inside other software. However, paid subscriptions do not provide unlimited usage, and some tasks still need human intervention.
Which subscriptions offer Grok Bot access?
Cursor Pro costs $20 monthly, while Pro+ costs $60 and Ultra costs $200. For teams, Standard costs $40 per user monthly, compared with $120 for Teams Premium.
All members of self-serve Cursor Teams plans can use the assistant. Enterprise customers can also request access through their account team.
On the Grok side, SuperGrok costs $30 monthly and SuperGrok Plus costs $100. SuperGrok Heavy also qualifies, while X Premium+ costs $40 monthly in the United States.
A usage-based free trial offers a seven-day window. However, Cursor measures trial credit through agent steps and tokens rather than a fixed message or job count.
Included usage resets each week. Users can continue beyond that allowance through their account’s shared on-demand spending, if they enable it.
How the assistant works and where it needs help
Each Bot runs on a persistent computer in Cursor’s cloud, with a browser, file system and terminal. Because it runs remotely, a task can continue after the user closes their own computer.
Users specify an outcome and provide access to the tools needed. The assistant can also retain context across conversations and repeat workflows on a schedule.
SpaceXAI suggests tasks such as researching sales prospects, checking customer records and drafting personalised outreach for approval. Other proposed uses include reproducing software bugs, preparing customer-health reports and compiling executive summaries from emails and calendars.
However, websites can block automation or require CAPTCHAs, logins and other human-only steps. The assistant can queue potentially consequential actions for approval before proceeding.
Early users have also reported workflows that need continued supervision. These practical limits mean users may still need to step in rather than leave every task running independently.
