Issue with Cursor Failing to Fully Load on macOS

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Dear Cursor Team,

I’ve been encountering an issue with the macOS version of Cursor where the application fails to start properly. The problem manifests in several ways:

  1. The integrated terminal fails to load.
  2. The search feature is unable to return any results.
  3. Source Control does not load properly.

There may be other related symptoms as well, but overall it feels like Cursor remains stuck in a continuous loading state.

In some cases, restarting the application once resolves the issue, while other times it requires multiple restarts before Cursor functions normally again.

I would appreciate any guidance or troubleshooting suggestions you may have.

Best regards,

Steps to Reproduce

  1. Launch Cursor on macOS.

  2. Wait for the workspace to finish loading.

  3. Attempt to use core features such as:

    • Opening the integrated terminal
    • Using global search
    • Accessing Source Control

  4. Observe that these features fail to load or remain unresponsive.

  5. In some cases, restarting Cursor resolves the issue temporarily, while other times multiple restarts are required.

Screenshots / Screen Recordings

screenshot-20260524-094100.png
screenshot-20260524-094100.png1356×680 10.5 KB

Operating System

MacOS

Version Information

Version: 3.5.33
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.1.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, this is a known session restore bug. If you had a git diff or Working Tree tab open when you closed Cursor, the next launch can get stuck during session restore and it blocks Terminal, Search, and Source Control. It’s cross platform, not just macOS.

Workaround:

  • Before you quit Cursor, close all git diff or Working Tree tabs, any diff tabs opened from Source Control.
  • If you’re already stuck, a restart usually helps because the stuck tab won’t be active during restore.

We’re tracking this bug. A fix that adds a timeout during initialization is already in progress, but I can’t share an ETA yet. I’ll post an update here once it’s fixed in a stable build.

8

Hey there!

We have merged a fix and are cherry-picking it back to 3.6. Please try again in a day or two (3.6.35+, not available yet) and let us know if the issue persists.