Planning next moves stuck

Same here. Just started crashing. I went back to an older version.
I was on Version: 2.1.49 and had to go all the way back to Version: 2.0.77

Since it looks like this happens all the time and I am loosing too much time and $ on credits, I think I will move to another IDE.

same here.
and my version:
Version: 2.1.50 (Universal)

VSCode Version: 1.105.1

Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770

Date: 2025-12-06T23:39:52.834Z

Electron: 37.7.0

Chromium: 138.0.7204.251

Node.js: 22.20.0

V8: 13.8.258.32-electron.0

OS: Darwin arm64 24.6.0

does anyone care about this?

I finally managed to fix this issue!

The Solution (Windows): The issue was caused by a corrupted local workspace cache/index. A hard reset of the workspace storage fixed it immediately.

1. Close Cursor completely.

2. Press `Win + R`, paste the following path, and hit Enter: `%APPDATA%\Cursor\User\workspaceStorage`

3. **Delete all files and folders** inside that directory.

4. Restart Cursor. After doing this, Composer is working perfectly again. Hope this helps anyone stuck in the same loop!

P.S. Just a heads up: this action cleared my local chat history and open tabs for the project, so be aware of that.

what worked for me… disable these extensions

Aikido Security
CodeRabbit

This fixed the issue! by now..

+1 Same issue here

Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

FINAL UPDATE: THE ROOT CAUSE FOUND (SOLVED)

I managed to fix the “Loading…” indexing issue permanently.

The Symptom:
My logs showed Activating extension 'anysphere.cursor-retrieval' failed: The specified module could not be found, even though I verified that the file file_service.win32-x64-msvc.node physically existed in the installation folder.

The Solution:
It was a missing system dependency. I installed the Microsoft Visual C++ Redistributable (x64) package.

Apparently, the indexing module (written in C++) could not run because my Windows was missing these libraries. After installing them and rebooting, the Indexing status immediately switched from “Loading…” to “Indexing,” and the Composer started working perfectly.

Check this if you are on Windows and stuck in the same loop!

AMAAAAZZZINGGGG - you are a legend, first solution to work!

same here.
Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

doesnt help for linux
Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.0-7-generic

this worked for me but on a mac the folder is ~/Library/Application\ Support/Cursor/User/workspaceStorage/

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

If I try to send a prompt with the Agent mode and select Plan and sent out the prompt, I see the plan being generated however the whole application where you cannot do anything.

I see the animated message “Planning next moves” but Cursor application is unresponsive and you need to close by Task Manager. I will get an error message presented by Task Manager: “The operation could not be completed. The operation is not valid for this process.”

After restarting the application, the plan is gone and I need to resend the prompt and gets stuck again - like a loop.
This happens also with a regualr chat.

Steps to Reproduce

Go the Agents Mode, give a prompt and select “Plan”. After creating the plan the app freezes and doesn’t continue and you cannot move the application window at all.

Expected Behavior

Well the usual, I should click and proceed, abort modifiy whatever.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (system setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Opus 4.5

For AI issues: add Request ID with privacy disabled

ba513325-2025-49ec-8c78-4cfb6edfb6b1

Additional Information

I have tried running Cursor with: cursor --disable-extensions but didn’t helped out.

I even have reinstalled the application completly but the issue persists.

Does this stop you from using Cursor

Yes - Cursor is unusable

@deanrie Thanks for coming back.

As requested here are the required information:

Request ID with Privacy turned off: 46efc858-e6d2-4d5c-867e-aa495ad4777a

Indexing panel status (green/error?) and if there are MCP servers in Settings (temporarily disable them)

  • Index - Green with 100%
  • Two MCP servers are disabled

Console errors:

Process explorer:

Regarding the troubleshooting:

  • VS Code Settings > search “HTTP/2” > enable “Disable HTTP/2”
    Didn’t helped out unfortunately.

  • Disable MCP servers (if any) and restart
    Didn’t helped out unfortunately

  • Close all open tabs/files and restart
    Didn’t helped out unfortunately.

  • Check Indexing: if there’s an error/“Initializing…”, try opening a smaller subfolder of the repo
    Didn’t helped out unfortunately.

I’d like to scroll in the console however both window console and process explorer hung up.

Also for your information that I am working on a local project, there aren’t any shares or network connectivity to other folders.

I have applied the registry key and after rebooting my device, it worked around ~ 40 minutes. However suddenly it got stuck again.

Request ID: d4572a97-d8bc-47b8-a9a1-71e6bb57d80d

It gets stuck everytime once answer by AI has been completed successfully and the chat has ended.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is not working, stuck on generating from time to time.
and it never solves itself. I will have to restart and rerun my notebooks. membership with a lot of remaining tokens.

Steps to Reproduce

in Cursor, Mac, the edit/generate function with command + K.

Operating System

MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

all models

Does this stop you from using Cursor

Yes - Cursor is unusable

I had no issues using version 2.0.11, but Cursor automatically upgraded me to the new version in the background, and now it’s unusable again. I can’t even turn off auto-updates—it’s really frustrating.

The new version of Cursor has this issue. I can revert to the old version, but Cursor automatically upgrades me. My newly upgraded Pro+ membership doesn’t work, so I recommend not using Cursor. I think it’s a piece of junk software.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is not working, stuck on generating from time to time.
and it never solves itself. I will have to restart and rerun my notebooks. membership with a lot of remaining tokens.

Steps to Reproduce

in Cursor, Mac, the edit/generate function with command + K.

Operating System

MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.39
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

all models

Does this stop you from using Cursor

Yes - Cursor is unusable

I’ve been reviewing your release history from the past year. It’s impressive in the same way a train derailment is impressive. The sheer consistency with which you ship broken software suggests either a complete absence of QA, or a QA team that exists purely for tax purposes. Every update is a surprise party where the surprise is “what critical functionality did we break this time?”

I’m not asking for perfection. I’m asking for the bare minimum: the ability to not automatically download whatever half-baked, untested artifact your CI pipeline spat out at 4:47 PM on a Friday before everyone left for the weekend.

Implement a toggle to disable auto-update. Some of us have actual work to do and can’t afford to spend Monday mornings reverse-engineering why your “minor patch” turned our workflows into abstract art.

Thank you

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The agent is stuck on ‘planning next moves’ and is not moving.

Steps to Reproduce

2+2

Expected Behavior

4

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.14
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.2.0

For AI issues: which model did you use?

auto

Additional Information

The error displayed in the console is as follows:"


{
    "error": {
        "name": "ConnectError",
        "message": "[invalid_argument] Error",
        "stack": "ConnectError: [invalid_argument] Error\n    at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12095:457498)\n    at async Object.getTeamAdminSettings (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:585:93853)\n    at async L6l (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:614:3706)\n    at async Veh (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:614:4236)"
    }
}
{
    "arch": "arm64",
    "platform": "darwin",
    "channel": "stable",
    "client_version": "2.2.14",
    "service": "aiserver.v1.DashboardService",
    "method": "GetTeamAdminSettings",
    "requestId": "not-found",
    "code": 3,
    "errorName": "ConnectError",
    "errorDetails": [
        {
            "type": "aiserver.v1.ErrorDetails",
            "value": {
                "0": 8,
                "1": 36,
                "2": 18,
                "3": 80,
                "4": 10,
                "5": 12,
                "6": 66,
                "7": 97,
                "8": 100,
                "9": 32,
                "10": 114,
                "11": 101,
                "12": 113,
                "13": 117,
                "14": 101,
                "15": 115,
                "16": 116,
                "17": 46,
                "18": 18,
                "19": 62,
                "20": 84,
                "21": 101,
                "22": 97,
                "23": 109,
                "24": 32,
                "25": 109,
                "26": 111,
                "27": 100,
                "28": 101,
                "29": 108,
                "30": 32,
                "31": 97,
                "32": 99,
                "33": 99,
                "34": 101,
                "35": 115,
                "36": 115,
                "37": 32,
                "38": 99,
                "39": 111,
                "40": 110,
                "41": 116,
                "42": 114,
                "43": 111,
                "44": 108,
                "45": 32,
                "46": 102,
                "47": 101,
                "48": 97,
                "49": 116,
                "50": 117,
                "51": 114,
                "52": 101,
                "53": 32,
                "54": 105,
                "55": 115,
                "56": 32,
                "57": 110,
                "58": 111,
                "59": 116,
                "60": 32,
                "61": 101,
                "62": 110,
                "63": 97,
                "64": 98,
                "65": 108,
                "66": 101,
                "67": 100,
                "68": 32,
                "69": 102,
                "70": 111,
                "71": 114,
                "72": 32,
                "73": 116,
                "74": 104,
                "75": 105,
                "76": 115,
                "77": 32,
                "78": 116,
                "79": 101,
                "80": 97,
                "81": 109,
                "82": 32,
                "83": 0,
                "84": 24,
                "85": 1
            },
            "debug": {
                "error": "ERROR_BAD_REQUEST",
                "details": {
                    "title": "Bad request.",
                    "detail": "Team model access control feature is not enabled for this team",
                    "isRetryable": false
                },
                "isExpected": true
            }
        }
    ],
    "errorDetailsDebug": "{\"error\":\"ERROR_BAD_REQUEST\",\"details\":{\"title\":\"Bad request.\",\"detail\":\"Team model access control feature is not enabled for this team\",\"isRetryable\":false},\"isExpected\":true}",
    "timeoutMs": "undefined"
}

Does this stop you from using Cursor

Yes - Cursor is unusable