Putting Cursor, Grok and X into one subscription can reduce the number of bills without necessarily reducing the total cost. The important questions are whether your usual models remain included and whether several products now consume the same allowance.
The X Subscription was announced on October 12; it did not launch today. It remains worth examining because community discussions on October 15 continued to question legacy-plan retention, shared usage and account unification. That demonstrates ongoing migration questions, not proof that any one person's allowance experience applies to everyone.
Available does not mean included
The current Cursor pricing page lists Plus at $8 per month, Premium at $30, Super at $100 and Ultra at $200, excluding applicable taxes. The page describes Plus as Grok-models-only. Premium and above still offer third-party models in Cursor, but that usage is outside the subscription price and billed separately at API list prices.
Consequently, “all third-party models have been removed” is inaccurate, as is “upgrading includes unlimited access to every model.” These are Cursor access and billing rules, not the model vendors' own subscription policies. Compare your actual model mix before comparing monthly fees. More product icons do not necessarily mean a larger allowance.
For example, a developer mainly using included first-party models and another relying on third-party models for long tasks could face very different additional costs on the same Premium plan. That is an analysis of usage patterns, not a measured average bill or a promise that the first pattern is always cheaper.
Separate monthly pools become shared weekly usage
The official legacy-plan documentation distinguishes the old Cursor system from the unified subscription. Legacy plans use monthly Cursor Models and Other Models pools; the unified subscription uses a weekly included pool shared with Grok, with third-party models billed separately. Not every legacy tier includes both pools, so check your particular plan.
The practical implication of sharing is that Cursor, the Grok apps and Grok Bot should not be treated as having independent bonus allowances. Spending in one place affects the shared remainder. A weekly reset is also different from a monthly billing cycle. Treating a month as exactly four weeks does not yield a reliable token or task allowance.
Published usage multipliers are not fixed request counts. Task length, model choice and workflow affect consumption, and this article has no basis for promising a number of coding jobs per tier. If the dashboard differs from expectations, retain usage details and account state for support instead of generalizing from another person's screenshot.
Account unification is not a reversible toggle
The official documentation says switching is optional. Your existing plan, price and features continue unless you change or cancel. A new public pricing page does not establish that every legacy customer has already been moved.
A completed switch to the unified subscription is permanent, however, and the documentation explicitly says support cannot undo it. If you have personal and work accounts or multiple Cursor identities, check the signed-in account, intended workspace and checkout details first. Do not complete unification merely to see what happens next.
Renewals, unused-time refunds, channel subscriptions and team identities have specific rules; do not reduce them to “every old subscription is automatically refunded.” App-store customers and people in multiple workspaces should consult the relevant migration instructions. Account and checkout information control; this article does not promise payment, refund or enterprise eligibility in any particular region.
Build a small usage ledger before deciding
Sample your previous billing cycle using four columns: base subscriptions actually paid, main models used, additional usage charges and product features you genuinely need. Mark missing records as unknown instead of inventing token counts. Then ask: which legacy allowances do I still use, which requests would become separately billable, and can the shared pool cover my busiest week?
The official additional-usage documentation says prepaid credit pays for third-party requests and applicable usage beyond the weekly pool. Automatic top-up must be enabled by the user. Check the prepaid balance, auto-top-up setting and monthly additional-usage limit rather than inspecting only the cancellation button. A usage limit, a recharge threshold and the base monthly fee are different controls.
Start with the current pricing page and unified subscription overview, and review the consequences before completing a switch. The site's Cursor listing and existing-project editing guide can help you revisit the workflow you need rather than changing plans for extra entry points you rarely use.
Our assessment is that the bundle is worth comparing for people who use several of its products, but there is no universal upgrade recommendation. Legacy customers who depend on third-party models should examine separate billing and the irreversible decision especially carefully. Whether the new plan is good value depends on their actual usage mix.