Grok Bot troubleshooting: every symptom and its fix

Most Grok Bot problems fall into one of nine buckets, and the first two checks are always the same: is there a declared incident, and are you on the latest app? Use the matrix below to match your symptom to its likely cause and fix, then jump to the detailed guide for that area. Everything here reflects official docs, the changelog through 0.78.1 (October 27, 2026) and attributed Cursor staff replies.

The short answer#

Before anything else:

1. Check for an incident. Look at status.x.ai (Cursor's status page moved there on October 26) and the forum's grok-bot tag. During a declared incident, wait.
2. Update the app. Settings → Updates → Check for Updates. The app and the Bot's computer update separately.
3. Open the computer view. Many "silent" Bots are waiting on a login, CAPTCHA, approval or question.
4. Follow the recovery order. Retry → restart the app → Recover computer → Update Bot's Computer → Reset, last.
5. Never Reset during an incident. Reset restores the last snapshot and can lose recent work.

Master matrix: symptom → cause → fix#

Won't respond#

A silent Bot has three main causes: it is waiting on you, the shared computer is unhealthy, or the service is degraded. The troubleshooting page adds a fourth: exhausted weekly usage with the on-demand limit reached. Open the computer view before changing anything.

Symptom → Fix

• Waiting on you → Answer the question, approval, login or CAPTCHA, or send a short redirect or "Stop now".
• "Failed to send" → Restart the app, send "Stop now" to the stuck Bot, and check status before resetting.
• Stuck in a loop → Ask what it last confirmed, the first failing step and whether it already made external changes, so a retry does not duplicate a draft or ticket.
• Quiet during long work → Since the October 11 release, Bots can show Waiting on results while a background command runs; that is not a hang.

Since 0.71.2, Stop ends background subagents too, and since 0.75.8 a status line appears right after you send. Full detail is in Grok Bot not responding.

Offline or unreachable computer#

Every Bot runs on one cloud computer per account, so its health decides everything. Follow the official order and stop as soon as Bots reply:

1. Choose Retry, or reopen the conversation.
2. Restart the app and check for an update.
3. Choose Recover computer when offered.
4. Otherwise, Settings → Computer → under Bot's computer, Update Bot's Computer.
5. Only then Reset Bot's Computer, accepting it can lose unsynced work.

On iPhone and Android the troubleshooting page names only Reset Computer under Settings → Bot → Bot Computer. Updating, recovering or resetting is otherwise a desktop job.

Your own Mac or PC shows offline when the screen locks, it sleeps, or the Grok Bot window is inactive for about 10 minutes. Click into the window; it reconnects in about a minute. Large file copies can also drop it for about a minute, so split them up. Check the status guide for the full incident log.

Sign-in and authentication#

Update to 0.75.2 or later first: browser sign-in now waits up to 20 minutes and handles corporate proxies better. Then check the account before the PC.

• Legacy Privacy Mode blocks Grok Bot; change the Cursor data setting, or ask your admin.
• Wrong or expired plan: Premium, Super and Ultra include Grok Bot; Plus and Free do not.
• VPN or proxy: if the phone works and desktop does not, try without it.
• October 30, 2026: sign-in moves to accounts.spacex.ai and accounts.x.ai; firewalled companies must allow them.

Walkthroughs and an IT allowlist template are in sign-in errors.

Routines#

Rule out incidents first; routines failed on Cursor's side on October 8, 9, 13 and 19, and missed runs are not replayed. Then check the routine is enabled, the time zone is right, plugins are authenticated, and nothing hit the hourly caps.

Approvals from unattended work expire after about 30 minutes. Test run performs real actions. See routines not running.

Usage and limits#

On The X Subscription, Grok Bot shares one weekly pool with Grok and Cursor. On legacy Cursor plans it has its own pool, but overflow bills from the shared on-demand pool. Usage is metered in steps and tokens, and every turn re-reads the whole conversation.

• Start a fresh chat per task and keep standing rules in the Bot's profile.
• Cut Bot-to-Bot messages and routine frequency.
• Set Auto Top-up, the monthly additional usage limit or on-demand deliberately; a legacy monthly limit is not a hard stop mid-run.

Numbers and settings are in usage limits.

Logins and passwords#

Isolation is per user, not per Bot, so every Bot can use every session on the shared computer. On October 5 a user found a Secure Form password in plain text in a page snapshot; staff said a fix was in progress, and no release note through 0.78.1 confirms one.

1. Choose Open the screen, press Take control, type the password and press Sign in yourself.
2. Never put passwords, codes or keys in chat.
3. Change any password you already entered through the Secure Form.
4. Prefer plugins: their OAuth tokens stay on Cursor's backend, not in browser cookies.

For sites that block the cloud browser by region, try Settings → Computer → Route traffic through this computer. More in shared computer.

Plugins, OAuth and MCP#

• Added but not working → Added only means installed. Choose Authenticate if it shows Needs auth or Disconnected; finish the browser sign-in within about 10 minutes.
• Multi-server plugins like Salesforce → Sign in to every row (since 0.75.5).
• Custom MCP server → Must be public HTTPS (streamable HTTP or SSE), OAuth only. Servers on your laptop or localhost are not attached.
• Empty HTTP 400 after connecting → Grok Bot omits the MCP-Protocol-Version header on reused sessions; staff confirmed it as open on October 8.
• Zoom error 4700 → Known issue, no workaround. SharePoint AADSTS50011 → Connect with Delegated permissions.

Setup and the full known-issues table are in plugins and MCP.

Gmail and Google Workspace#

• "Admin needs to review Grok" or "Access blocked" → A Workspace admin opens Security → Access and data control → API controls → Manage third-party app access, adds Grok and sets it to Trusted. Switching browsers does not help.
• Links become google.com/url redirects → Open as of October 16; re-paste links in Gmail before sending.
• Bot cannot read an attachment's contents → Known gap; use the browser or route the file through Drive.
• IMAP or SMTP scripts time out → The HTTPS-only outbound issue; the Gmail connector still works.
• Expected a send, got a draft → Since 0.75.5, sends from routine turns wait as drafts.

Details in Gmail and Google Workspace.

Mobile limits#

The iPhone, iPad and Android apps share the same Bots, routines and computer, but some things need desktop:

On iPhone 1.18.0 with iOS 26 or later, Settings → Vault shows no Save button for a new login; it is fixed in 1.19.0. Install details are in download.

Copy-paste triage brief#

Pause the current approach. Tell me:

1. The last action you confirmed succeeded.
2. The first step that failed, with the exact visible error.
3. Any changes you already made outside this chat (drafts, messages, files, tickets).

Do not repeat any write and do not reset the computer.

Suggest one small, read-only check that tells missing access apart from

unavailable data or a changed interface. If you need me, name the exact action.

Before you report a bug#

• Grok Bot version and operating system
• Exact error text and the Bot or routine name
• Approximate time and your time zone, plus any request or conversation ID
• Whether Retry, a restart or Update Bot's Computer changed anything
• No passwords, one-time codes, private keys or secrets

Our take#

Diagnose before you act: check the status page and forum, update, and open the computer view before you touch a single recovery button. Reset is almost never the answer, and during an incident nothing you do locally helps. When a symptom is not in this matrix, post your version and timestamp in the matching forum thread rather than experimenting on your only cloud computer.

Frequently asked questions#

Why did all my Grok Bots stop responding at once?#

Every Bot on an account shares one cloud computer, so when it is stuck, unreachable or mid-update, all Bots fail together. Check status.x.ai and the forum for an incident first. If nothing is declared, follow the recovery order: Retry, restart the app, Recover computer, Update Bot's Computer, and only then Reset.

Should I reset the Grok Bot computer?#

Only as the last step. Reset restores the last saved snapshot and can lose recent or unsynced work, while Recover and Update preserve durable files and logins. During October incidents Cursor staff asked people to hold off on Update, Recover and Reset entirely, because the fault was on Cursor's side and resending the message was enough.

How do I tell a Grok Bot outage from a problem on my account?#

Compare timestamps on status.x.ai, where Cursor's status page moved on October 26, and the Cursor forum's grok-bot tag. If many people report the same symptom in the same hour, wait. A green status page only means nothing has been declared; on September 16 the first forum report came about three hours before the incident opened.

Why does one Grok Bot always fail while the others work?#

Usually its conversation, not the computer. Cursor staff traced October cases to the model provider's safety filter refusing that Bot's history, for example security or biology research content. Resetting does not help. Start new work in another or a new Bot, do not ask other Bots to read that chat, and do not delete it. Since 0.71.2 the app shows Blocked by a safety check.

What should I include when reporting a Grok Bot problem?#

Your Grok Bot version and operating system, the exact error text, the Bot or routine name, the approximate time with your time zone, any request or conversation ID, and whether Retry, a restart or updating the Bot's computer changed anything. Leave out passwords, one-time codes, private keys and secret values.