Fix Grok Bot X plugin OAuth when access fails

First-time X sign-in lives in Connect your X account in Grok Bot. Use this page when the plugin is already there and the browser returns Something went wrong or failed to give the app access.

Official reconnect

Official troubleshooting for a plugin that will not install or authenticate:

1. Open Settings → Plugins. Confirm X is installed.
2. Open the plugin detail page and choose the authentication action.
3. Finish authorization in the browser with the intended X account.
4. Return to Grok Bot and retry.
5. If your org provides the plugin, check the admin-configured variable.

If authentication was revoked in X, remove and reconnect the plugin. When you no longer need X in Grok Bot, uninstall the connector and revoke authorization in X.

Installed connectors are account-wide. Paid Grok Bot users get free X API credits to start.

Staff reconnect when the browser still fails

Cursor staff, on the official X plugin OAuth threads:

1. Update Grok Bot (staff cited iOS 1.2).
2. Open the X plugin → connected account → disconnect / sign out → sign in again fresh.
3. Uninstall and reinstall the plugin. Staff (Sep 1): that “tends to kick it back to shape, at least for a little while.”

Staff are tracking desktop, Cloud, Grok Bot, and X-side app config.

Cloud Agents

Cursor staff: Cloud Agents cannot complete interactive MCP auth. Connect the X plugin from desktop or the dashboard, then share it to cloud. There is no documented clean workaround if that still fails, and no published timeline.

Pitfalls

• A Cloud Agent turn will not pop an X OAuth window.
• Uninstall/reinstall is a staff workaround. Staff called it temporary.
• One X sign-in covers every Bot on the account.