Grok Bot 0.71.2 – Persistent login loop / constantly kicked out + “unable to load” (Windows 11)

Account & Billing
,
1

Where does the bug appear (feature/product)?

Something else… → Grok Bot (desktop app)

Describe the Bug

Persistent login / authentication loop on Grok Bot 0.71.2.

The app frequently kicks me out. Sometimes I can briefly get in and even successfully run “Update Grok Bot’s Computer”, but shortly after it logs me out again. Other times, right from the home screen it shows an error like “unable to load” / “impossibile caricare” and immediately kicks me out.

Steps to Reproduce

  1. Open Grok Bot 0.71.2 on Windows 11
  2. Sign in (sometimes succeeds briefly)
  3. After a short time (or immediately), the app logs me out or shows “unable to load” and forces me to log in again
  4. Even after successfully updating the Bot’s Computer, the issue returns

Expected Behavior

I should stay logged in stably and be able to use Grok Bot without being constantly kicked out.

Operating System

Windows 10/11 → Windows 11

Version Information

Grok Bot version: 0.71.2

Additional Information

I have already tried extensively:

  • Update Grok Bot’s Computer (multiple times)
  • Recover computer
  • Full Sign out + Sign in
  • Complete uninstall + deletion of AppData and LocalAppData folders
  • Restart PC
  • Testing without VPN, proxy and antivirus
  • Login in Incognito mode

The problem is intermittent but keeps recurring. Client-side troubleshooting is exhausted. A backend session / computer reset seems needed.

Does this stop you from using Cursor?

Yes - Cursor is unusable (Grok Bot is unusable)

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!

8

Hey @k3n0taku-sketch

This isn’t the Grok Bot app itself, and it isn’t anything you did wrong. The pattern you’re describing (a successful sign-in that gets dropped a minute or two later, over and over) is something we can look into on the account side. Your Grok Bot computer and its files are intact.

Because getting to the bottom of this needs an account-level look, could you email us at [email protected] and reference this thread? We’ll take it from there and get you unblocked.

A couple of things that help in the meantime:

  • If you use any Cursor API keys (for the CLI, a script, or a third-party integration), rotating them in your Cursor dashboard is a safe first step. A tool still holding an old key can sign your sessions out in the background.
  • Please hold off on “Recover computer” and “Update Grok Bot’s Computer” for now. Your files are fine where they are, and those actions can risk unsynced work. Once this is sorted, the computer will reconnect on its own.