IDE has stopped working, constant spinning wheel

Support Bug Reports
,
1

I have been using the ide for sometime and Tool sandbox was suddenly not able to run commands, and I downloaded latest and now its not working anymore, I am seeing a constant spinning wheel and it does not let me get control of the edits to type anything. I have reinstalled/restarted/force quit and its not helping.

Where does the bug appear (feature/product)?

  • [ ] Cursor IDE

  • Cursor CLI

  • Background Agent (GitHub, Slack, Web, Linear)

  • BugBot

  • Somewhere else…

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

Not able to use it at all, just shows a spinning wheel

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

  1. download latest version

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

Unable to check the version, I installed the latest version today from website

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

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)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere 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!

4

Hey, thanks for the report.

Since you can’t open the app itself, let’s try via the command line:

  1. Launch with extensions disabled:
cursor --disable-extensions

This will help confirm whether extensions are causing it.

  1. Check Activity Monitor:
  • Open Activity Monitor
  • Find the Cursor processes
  • Which one is using the most CPU or RAM?
  1. Crash logs (if any):
ls -lt ~/Library/Logs/DiagnosticReports/Cursor* | head -5
  1. Try rolling back to a previous version:
    Download the stable version from Download · Cursor. It might be an issue with the latest update.

Send what you see in Activity Monitor, and whether it launches with --disable-extensions. That’ll help narrow down what to check next.