Grok Bot Unable To Authenticate via Gmail Plugin

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?
Grok Bot

Describe the Bug
Grok Bot is unable to authenticate to Google accounts using the Gmail plug-in

Steps to Reproduce

  1. Install Grok Bot and authenticate
  2. Click Plug-ins and add the Gmail plug-in
  3. Add an account and attempt to authenticate to a personal Google account

Result
Error Message from Google: This app is blocked. The app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.

Screenshot

botauth
botauth1548×692 24.2 KB

Operating System
Mac OS Tahoe

Does this stop you from using Grok Bot
Yes.

Additional Information
Cursor and Grok Bot seem to be sharing some level of data for the plug-in, as a workaround we can authenticate to a single account in Cursor using the local authentication method, however at this point there seems to be no mechanism to authenticate to multiple Google accounts within Bot.

Seeing many other users affected on X.

grokbot
grokbot1920×1340 257 KB

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey @Shopticon, thanks for the detailed report and the screenshot! I’ve flagged this to the team.

Your workaround is a good one in the meantime: authorizing Gmail from Cursor goes through a different authorization path that isn’t affected, and the connection is shared with Grok Bot.

On multiple accounts: once authorization from Grok Bot is working again, you can add more Google accounts from the Gmail plug-in’s page in Grok Bot (“Add Another Account”).

We’ll follow up here once it’s resolved!

7

Hi @Colin I’m trying to get Grokbot to connect with personal gmail and getting that error. I don’t have a paid cursor account (I don’t really use cursor) - what options are there please? This feels like a big stumbling block for new GrokBot (since you added the new plans) users ? Thank you,

8

“Hi Colin, thanks for looking into this. I tried the suggested workaround of connecting my Google account directly through Cursor’s main settings, but unfortunately, it’s still not working for me. Any ETA on when the direct plugin authorization will be fixed?”

9

This seems to be resolved now after the app update today.