XPASS leak suggests shared X Grok and Cursor subscription
Four proposed XPASS tiers appear in Nima Owji’s report. Pricing and release timing remain unconfirmed.
An XPASS report proposes bundling X, Grok, Cursor and Grok Bot. Independent researcher Nima Owji shared the alleged subscription design on October 1. Its origin and release plans remain unconfirmed.
The graphic shows four tiers with placeholder prices. Premium lists shared usage across products. Owji describes Plus as four times Premium usage, Super as fifteen times and Ultra as fifty times.
ByteForward reviewed the original public post and image. No inspectable build or code change accompanies them, so the interface has not been independently authenticated inside X.
Image shared by Nima Owji on X
View the original source post on X
What the companies currently document
X’s current Premium help page still describes three tiers called Basic, Premium and Premium+. Premium+ includes SuperGrok access and Grok Bot. It does not describe the four XPASS tiers shown in Owji’s report.
Some bundling already exists for Grok Bot, the persistent agent product. In its August 26 Grok Bot announcement, SpaceXAI extended access to eligible SuperGrok and Cursor subscriptions. That announcement explicitly gives Grok Bot its own usage allowance, separate from the subscriber’s Grok and Cursor usage.
There is also a documented account integration underway. Cursor’s help center says its login moves to SpaceXAI account domains from September 30, with the former login remaining as a network compatibility fallback until October 30. That establishes an account change, but offers no confirmation of XPASS pricing or entitlements.
Why the allowance details matter
A useful comparison would need a price, a defined allowance and rules for measuring each kind of task. A multiplier alone cannot tell a subscriber how many coding jobs, chats or videos fit into a billing period. Migration rules would also matter for anyone already paying for several eligible services.
A common allowance could make several subscriptions easier to manage. It could also mean a demanding coding session leaves less capacity for another service. That is the practical question an eventual launch would need to answer. Until final terms appear, subscribers cannot reliably compare the proposed bundle with what they already pay for.
