When Access blocked appears after Premium+ SSO

X Premium+ and xAI can finish authorize, then authenticator.cursor shows Access blocked, please contact support and no Grok Bot session starts. The same block can hit iOS and Windows together. Forum automation on 171289 routes these cases to email support because the forum team cannot clear authentication locks.

What to send support

Email hi@cursor.com (continue an existing thread if you already opened one). Include:

• The email address used for the Grok Bot / Cursor sign-in
• The X Premium+ handle that authorized
• Surfaces and app versions (for example iOS and Windows build numbers)
• That X and xAI authorize succeeded, then Access blocked appeared on authenticator.cursor
• Any open ticket id from a prior mail

Ask whether the account has an email mismatch, a permanent link on another Cursor account, or a phone-verification lock. You are asking to use an existing Premium+ grant, not extra usage.

Steps that do not clear the block

Sign out, quit, reinstall, and switching between system browser and in-app browser failed for the reporter on that thread. Keep those off the loop once you have mailed support with the details above.

Distinct banners

The in-app Authentication error / try logging out and back in banner after you are already signed in follows Fix Grok Bot Authentication Error login loop (often Update Grok Bot’s Computer). Access blocked on the authenticator host before a session exists is the support path on this page.

Pitfalls

• Opening duplicate forum threads after the auto-reply already pointed you at hi@cursor.com
• Burning reinstall cycles while a ticket sits unanswered