Fix Grok Bot Cloud Agent “Privacy Mode (Legacy)” when Settings show current Privacy Mode

Grok Bot refuses a Cloud Agent launch with “Cloud agents are not supported in Privacy Mode (Legacy).” Cursor Settings → Privacy already shows the current Privacy Mode Active wording (no training; code may be stored for Cloud Agent and related features). The same account launches a Cloud Agent from Cursor Desktop on the same repo without error.

What staff confirmed

Cursor staff (deanrie, Sep 3, 2026, forum thread 170486) reviewed the Privacy screenshot and said the account setting is correct. The failure is on the Grok Bot launch path: a recent release incorrectly hits the Legacy Privacy check for Bot-launched Cloud Agents. Desktop launch is unaffected.

Staff said you do not need to sign out, switch Privacy Mode, or reset. Those steps will not clear this false check.

What to do while the Bot path is broken

1. Confirm Cursor Settings → Privacy shows the current Privacy Mode (not Legacy).
2. Launch the Cloud Agent from Cursor Desktop (Cloud dropdown / Agents) on the same repo.
3. Retry the Grok Bot Cloud Agent launch later. If the Legacy error returns, reply on the forum thread with the time of the attempt so staff can re-check.

When Legacy is real

A genuine Legacy Privacy Mode block during Grok Bot sign-in or setup is a different wall. Bot requires cloud data storage and does not support Legacy Privacy Mode. Move the Cursor account off Legacy, or ask an org admin if the policy is managed. See Finish Grok Bot sign-in and clear Legacy Privacy Mode.

Pitfalls

• Desktop Cloud Agent working while Bot launch fails is the signature of this false check.
• Toggling Privacy Mode or Reset will not fix a Bot-path false Legacy hit once Settings already show current Privacy Mode.
• “Can’t reach your computer” points at the hosted Agent Computer. For that path see Fix Grok Bot “Can’t reach your computer”.