After an account merge, older bots stick on Working on it

If you merged your Cursor account into The X Subscription and your older bots now sit on "Working on it…" forever, leave them alone. Cursor staff confirmed at 6:04 PM ET that "the final step of the merge didn’t finish re-linking them to your merged sign-in," and asked affected users to "please don’t reset, delete or recreate them in the meantime." If something can't wait, make a new bot for that one job.

• Who: people who merged an existing Cursor account (with bots) into the new subscription account.
• Symptom: bots made before the merge accept messages but never start. Bots made after the merge reply normally.
• Routines too: "Scheduled routines on those older bots are affected the same way."
• Data: staff say "your bots, their conversations and their computers are all still there."
• Fix: flagged to the team, no timeline yet.

Update, Oct 14: Fixed. At 8:34 AM ET Colin said "The fix has now gone out to every affected account," so older bots "should reply again." Messages sent while they were stuck "won't be picked up on their own," so send each older bot a new message and test its routines (what to do now).

What changed#

At 5:41 PM ET, qwaverob reported that after moving from Cursor Pro+ to the new subscription and merging accounts on the same email, "all 12 of my existing bots became completely unresponsive," across desktop, web and mobile. Their test put a migrated bot and a brand-new bot in one group chat with the same instruction: the new bot answered, the old one stayed stuck.

Staff member Colin replied that the problem is the merge itself: "Messages to them are accepted but never start, which is why bots created after the merge work and the older ones sit on “Working on it…”." At 7:47 PM ET a second user wrote, "I have the exact same problem after the merge."

Why it matters#

The merge is how existing Cursor customers get onto The X Subscription, and the bots most likely to be hit are the ones people rely on most: older bots carrying months of instructions, skills and routines. Because scheduled routines on those bots also stop, a morning digest or a weekly report can silently skip without any error in chat. The natural instinct, resetting or rebuilding the bot, is exactly what staff say won't help.

What to do now#

1. Send each important older bot a short test message, like "Reply with exactly WORKING."
2. If it sticks on "Working on it…" or "Not delivered yet," don't reset its computer, delete it, or recreate it. Staff say that "won’t help here."
3. For anything time-sensitive, create a new bot and give it that one task. Staff say "there’s no need to move anything over," so don't migrate skills or files wholesale.
4. Check which routines live on the stuck bots, and run anything urgent by hand or from the new bot until the fix lands.
5. Add your case to the forum thread so staff can include your account.

Example prompt for a new bot:

My older bots stopped responding after my account merge. Until they're fixed, take over this one task: [describe the routine and its schedule]. Don't copy anything else over.

Good to know#

• Holding off on the merge? Staff haven't said whether new merges still hit this. If your bots matter day to day, waiting for the fix is the cautious choice.
• A separate report tonight, Bot failed to respond on every message plus failing to create bots, got a staff reply at 6:31 PM ET: "This one is on our side, not your computer! A fix is being deployed." That case didn't mention a merge, and new bots failed too, so it is a different problem.
• Merging accounts was a user wish we tracked on October 9. It arrived with The X Subscription on Oct 12. Cursor's help center says eligible Cursor and Grok accounts are combined when you switch. This is its first staff-confirmed bug.

What to watch#

Colin said "I’ll follow up here as when there’s an update." We'll update this piece when staff post the fix, and note whether routines that missed runs get replayed.