METAGROK
GROK BOT / switch-slack-github-from-free-cursor-to-ultra-for-grok-bot

Grok Bot

Switch Slack and GitHub from a Free Cursor account to Ultra for Grok Bot

switch-slack-github-from-free-cursor-to-ultra-for-grok-bot

Grok Bot and Cloud Agents need an eligible paid plan on the Cursor account that owns the integrations. Eligible plans (Bot FAQ): SuperGrok Plus, SuperGrok Heavy, Cursor Pro+, Cursor Ultra, and Cursor Teams Standard or Premium. Official metering: Plans and billing.

When Slack (or GitHub) was first connected on a Free Cursor account, and Ultra / Heavy lives on a different email, Slack can stay stuck on the Free side. Managing Slack from Free can hit a Pro paywall. There is no documented dashboard button that transfers Slack between Cursor accounts — community self-fix from forum 172712 (SmokedMeats, Sep 22–23, 2026).

Before you start

  1. Confirm Ultra (or another eligible plan) is active on the destination Cursor login you want Bot to use.
  2. List what still lives on the Free account: Slack workspace link, GitHub app install / repo scopes, any Bot chat history you care about exporting first.
  3. Expect to reconnect integrations on the paid account after the Free account is gone — removing Slack only inside Slack is not enough if Cursor still binds the workspace to Free.

Move integrations to the paid account

OP-verified sequence on 172712:

  1. Delete the old Free Cursor account (the one that held Slack), after you have anything you need from it.
  2. Update your Cursor forum email (and any other Cursor-linked profile email you still use) to the Ultra / Heavy account email so support and forum identity match the paid login.
  3. Remove and re-add GitHub on the Ultra Cursor account, then re-scope the repositories Bot / Cloud Agents should reach.
  4. Reconnect Slack while signed into the Ultra account (same install flow you used the first time), then open Grok Bot and a Cursor Agent window and confirm both run under the paid plan.

Retest

  1. In Grok Bot, send a short hello and confirm a reply (not a plan / can’t-reach failure).
  2. Open Settings → Usage (or cursor.com/dashboard) on the Ultra login and confirm Bot usage meters there.
  3. Trigger a Cloud Agent or Slack-side Bot ask that previously failed on Free; confirm it uses the Ultra account.

Pitfalls

  • Do not invent a “transfer Slack” control in Cursor settings — none is documented; the working path so far is delete Free → reconnect on Ultra.
  • Removing the Slack app only from Slack’s side can leave Cursor’s Free binding in place.
  • GitHub scopes do not auto-follow a deleted Free account — re-add and re-scope on Ultra.
  • First-time Slack install without an account switch is covered by Add Grok to a Slack workspace.