Topics ▾
Workflows ·

Before you unify your Cursor, Grok and X subscriptions

Beginner, 15 minutes

A walkthrough of the unify screen: connect the right accounts, compare plans, watch third-party model pricing, and know it can't be undone.

How this helps you

You go into the switch knowing which account to connect, what you'll pay after the intro price, and what isn't included.

✦ Try it
I'm deciding whether to unify my Cursor, Grok and X subscriptions. What I pay now: [current plans and prices]. How I use them: [which models and tools, and how often I run out]. The plans on my unify screen: [plan names, prices, intro period]. Compare staying as I am with each plan, flag what changes for third-party models like Claude or GPT, and remind me what happens when the intro price ends. Don't sign me up for anything.

Fill in: [current plans and prices]: each subscription you pay for. [which models and tools]: e.g. Grok Bot daily, Claude in Cursor weekly. [plan names, prices, intro period]: copied from the unify screen.

What they did

Carl Taylor recorded himself moving his separate Cursor, Grok and X Premium subscriptions into one unified plan. He went to cursor.com/unify, logged in and clicked Get started, and the screen offered to connect his Cursor, Grok and X accounts. He hit a snag: he had two Grok accounts, one using his X login and one using the Google login he used for Cursor. It only worked once Cursor stayed on Google and Grok and X shared the same login. The next screen compared his current plans and spend with the new ones, and he points out it defaults to a pricier plan. Third-party models such as Claude or GPT are billed separately at API pricing, not included in the plan's usage. Linking is permanent. His price was an intro rate for 6 months that then goes up, and he skipped the offer to add credits at the end.

Who it's for: Anyone paying for two or three of Cursor, Grok and X Premium who is considering the unified plan.

Before you start

How to try it

  1. Write down what you pay now and which models you use, especially Claude or GPT.
  2. Go to cursor.com/unify, log in and click Get started. Check every account it matches before you click Connect; use a different one if it picked the wrong account.
  3. On the plan screen, compare your current spend with each plan instead of taking the default. Note the intro price and what it rises to.
  4. Read the checkboxes: linking is permanent, and third-party models are billed separately.
  5. At the credits offer, choose Finish without adding credits unless you want them.

What to expect

A short table of stay versus each plan with monthly cost now and after the intro period, plus any warning about third-party model costs.

Common mistakes

Related tips

Worth knowingCarved from a segment of this video starting at 0:00. Paraphrased by us; watch the original for the full walkthrough.
Next in Workflows →Fact-check before you publish

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips

Related Grok Bot tips

More Workflows →
Workflows

Two habits that make usage last: batch requests, send words not screenshots

Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.

How this helps you The same work uses fewer messages and less image reading, so your weekly usage goes further without dropping any jobs.
Spotted by Sharbel A. (YouTube) · 3 Nov 2026
Workflows

Let your Bot cancel free trials and unused subscriptions

Three built-in templates from 0.78: start a trial and cancel it before it bills, cancel plans you don't use, and watch renewal prices.

How this helps you You stop paying for trials and plans you forgot about, and nothing is cancelled without your OK.
Spotted by @spectnfa · 31 Oct 2026
Workflows

From support form to fix: a webhook, a Bot and a Cursor cloud agent

A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.

How this helps you By the time an engineer looks at a bug, it has repro steps, a test and a proposed fix waiting.
Spotted by Grok, Santi Garza (YouTube) · 29 Oct 2026