I didn’t set out to migrate my Cursor subscription.
I didn’t even plan to change anything about my development setup.
This whole story started because I wanted to install Grok Bot on my phone.
Instead of opening the account I was already using, the mobile flow ended up creating or selecting another account under the same email. Suddenly, Cursor, Grok, and Grok Bot were no longer where I expected them to be.
So I contacted support.
That was the moment a small account issue turned into a much bigger billing problem.
Nine days earlier, I had bought Cursor Ultra
On November 7, 2026, I purchased Cursor Ultra through a discounted offer.
The normal price was around $200, while I paid roughly $100.
For the way I use Cursor, that was a very good deal.
Cursor had already become one of my main coding executors. I use AI heavily for implementation, debugging, repository work, testing, and longer development sessions, so the larger Ultra allowance wasn’t something I bought “just in case.”
I actually needed it.
When the duplicate-account problem appeared after installing Grok Bot on my phone, my goal was simple: fix the account situation without losing the Ultra subscription I had just paid for.
Support told me to merge the accounts
The first support agent I spoke with was an xAI AI-support agent named Sam.
I explained the situation and was directed to use the account merge flow.
The reassurance I received was very clear:
“Nothing has been lost.”
So I followed the support instructions.
After the merge, my Cursor Ultra subscription was gone.
I received a refund of $70.19, and the merge itself turned out to be permanent.
At that point, this was no longer a simple sign-in problem.
Cursor and Grok are now part of a much closer subscription system
On October 12, 2026, xAI announced The X Subscription, bringing Grok, Grok Bot, Cursor, and X Premium into a shared subscription ecosystem.
The concept itself makes sense.
One account, one subscription, and shared access across several AI products can be much simpler than maintaining separate accounts and bills.
But existing Cursor users are not starting from zero.
They may already have old plans, annual subscriptions, promotional pricing, multiple accounts, or separate Grok and Cursor identities.
That makes migration much more sensitive than creating a brand-new account.
And apparently I wasn’t the first person to discover that.
I found the previous reports too late
Only after my own merge did I start searching the Cursor forum for similar cases.
There were already users reporting account-unification problems in late October.
Some described Grok Bots ending up on one account while the paid plan was attached to another. Others reported that parts of their previous account state were no longer available where they expected them after unification.
By October 27, Cursor staff had publicly acknowledged problems affecting some account migrations.
That was the frustrating part for me.
The problem wasn’t completely new by the time I encountered it.
I simply learned about those precedents after completing an operation that cannot be reversed.
The official documentation makes my case even more confusing
The current documentation makes an important distinction between several actions: signing in, linking accounts, collapsing multiple Cursor accounts, and switching plans.
According to the documentation, account collapse by itself does not switch your plan or cancel an existing subscription.
Subscription changes are supposed to happen separately as part of an eligible checkout when switching to The X Subscription.
The same documentation also says completed unification is permanent and cannot be undone by support.
That combination is exactly why I have now escalated the case to billing.
I don’t want to speculate about which internal step caused my Ultra plan to disappear. That is something the billing team needs to investigate.
From my side, the sequence is much simpler:
I had an active Ultra plan.
I had an account problem after trying to use Grok Bot on mobile.
Support recommended a merge.
I followed the instructions.
Ultra disappeared.
The $70.19 refund did not put me back where I started
The refund also needs some context.
xAI’s documentation explains that when an old subscription is cancelled during a plan switch, the unused part of the billing period can be refunded on a prorated basis.
That appears to be what the $70.19 represents.
So this is not really compensation for losing a discounted Ultra plan.
It is closer to a refund for the unused days of the subscription.
The difference matters because I paid roughly $100 for Ultra under a promotional price.
Getting $70.19 back does not give me the ability to simply purchase the same plan again under the same conditions.
Premium feels very different for my workload
Right now, the plan I still have is Premium purchased through Apple.
It remains active until December 15, with renewal disabled and no additional prepaid credits.
Under the new model, Grok, Grok Bot, and supported Grok usage in Cursor share a weekly usage pool. Third-party models such as Claude or GPT inside Cursor require separate credits.
For a light user, that may be completely fine.
For my development workload, the difference became visible almost immediately.
Earlier, after roughly an hour and a half of active work, I had already used about 18.8% of the Premium weekly allowance.
Now, despite working much less intensively because of this entire issue, I am already at 38% of the weekly limit.
The next reset is Monday, November 23.
That changes how I work.
Instead of thinking only about the development task, I now also have to think about whether the next coding run is worth spending part of the remaining weekly pool.
Avoiding exactly that kind of calculation was one of the reasons I bought Ultra in the first place.
This is not a “Cursor is bad” post
I want to make that very clear.
I like Cursor.
That is why I bought Ultra and why losing the plan is actually a problem for me.
I also don’t think The X Subscription is automatically bad.
For someone actively using Cursor, Grok, Grok Bot, and X, having a single subscription and shared usage pool may be genuinely useful.
My issue is with the migration experience.
When an account operation is permanent and can affect a recently purchased subscription, the user needs to understand exactly what will happen before confirming it.
In my case, I contacted support precisely because I didn’t want to make a mistake.
Following that support recommendation left me in a worse state than before I asked for help.
Billing still has a chance to resolve this properly
My support ticket, T-K32987, has now been escalated to a human billing specialist.
I’m not asking for anything excessive.
Any one of these outcomes would resolve the issue for me:
- restore an equivalent Ultra subscription at the price I paid;
- provide enough credit or discount to restore the equivalent plan;
- refund the full amount I originally paid, roughly $100.
That’s it.
I don’t want free months or some huge compensation.
I simply don’t want to lose money or working capacity because I followed the instructions given by support.
If billing resolves it properly, I will update this article. I think it is only fair to document the resolution as clearly as the problem.
The bigger lesson for me is about dependency
This incident made me think about something beyond billing.
Over the last few months, I have been trying to make my AI-development workflow less dependent on any single model or coding agent.
Until now, I mostly thought about that as a technical problem.
Maybe Cursor is better for one type of task, Claude Code for another, Grok for research, or Codex for something else.
But subscription systems, usage limits, account migrations, and pricing changes create another kind of dependency.
You can build a very good development workflow around one tool and still discover that a billing or account issue can suddenly block a large part of your work.
That is why I have now started looking more seriously at Claude Code as an alternative executor.
Not because I suddenly dislike Cursor.
Because I no longer want one subscription to determine whether I can continue development that day.
What I would do differently now
If I could go back to the moment before the merge, I would not click it nearly as casually.
Especially if you currently have:
- a legacy Cursor plan;
- promotional pricing;
- multiple Cursor or Grok accounts;
- an Apple or Google Play subscription;
- an existing Ultra or annual subscription.
I would first verify exactly which account becomes primary, which subscription survives, whether a plan switch is involved, what refund will be issued, and whether the old plan can still be purchased afterward.
The official documentation now explicitly says that completed unification is permanent.
That alone is a good reason to treat the button with much more caution than I did.
My story started with something completely ordinary: I wanted Grok Bot on my phone.
A few steps later, I had lost the Cursor Ultra plan I bought nine days earlier.
Maybe billing will fix everything and this will end up being nothing more than an annoying migration bug.
I hope so.
But for now, my first experience with the new Cursor + Grok account system has taught me one very practical lesson:
an AI coding workflow should not depend so heavily on one account, one subscription, or one executor that a billing issue can stop development.
Top comments (1)
Cursor forum unlisted my account merge issue
Small update to my Cursor + Grok account merge story.
I posted my case on the Cursor community forum because I wanted to understand whether other users had experienced the same problem after account unification.
The thread was quickly unlisted.
The official forum response was that the issue appears to be specific to my account, the forum team does not have access to subscription or account details, and I should continue working through my existing support ticket with
support@x.ai.That is reasonable from a privacy point of view.
But it also means that cases like this are difficult for users to compare publicly.
My situation is still unresolved:
I already found older public reports of account-unification problems, so I still do not know whether my case is truly isolated or simply handled privately one user at a time.
For now, I’m waiting for the billing team.
I’ll update the original article when there is a real resolution.