Account soft-banned - stuck on "Planning next moves" (Ultra Plan)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

My account appears to be soft-banned. When I input any prompt in Cursor, it only shows “Planning next moves” and never produces any output. However, when I log into the same account on a different machine, everything works normally. I am an Ultra Plan subscriber and have not violated any terms of service to my knowledge.

Steps to Reproduce

  1. Log into my Cursor account on my primary machine
  2. Open any project
  3. Type any prompt in the AI chat
  4. Observe that it only displays “Planning next moves” indefinitely
  5. Log into the same account on a different machine - it works fine

Expected Behavior

The AI should respond normally to my prompts, as it does when I use a different machine with the same account. As an Ultra Plan subscriber, I expect consistent access across all my devices. If this is indeed an intentional account restriction, I request a clear and explicit explanation of the reason. It is unreasonable to silently restrict a paying user’s access through what appears to be a bug, rather than providing transparent communication about any policy violations or account issues.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.19
VSCode Version: 1.105.1
Commit: 77af5775de140fced9aeb1a50e372883667d6810
Date: 2026-01-02T18:36:40.946Z
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 this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Try clicking the buttons in Cursor Settings / Network

I am using the same account on the same network, but on two different machines. This main machine cannot run it, while the other one works perfectly fine. If my account has been banned, I believe that as an Ultra Plan user, you should at least give me a clear explanation.

back to cursor Version: 2.2.44, every things is ok, bug i lost a lot chat log.

1 Like

Looks like this link seems to cover the same issue…

2 Likes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Use any model that’s not Composer 1, and the planning next move phase lasts about 3-5 minutes at a time.

Steps to Reproduce

Use any model and wait for planning next moves.

Expected Behavior

It takes maybe up to 15 seconds, not 3-5 minutes.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.18
VSCode Version: 1.105.1
Commit: df371ac0d93fe1a68d05eeb59a09c5c39add0c80
Date: 2026-01-01T01:49:45.089Z
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.2.0

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

"Yesterday afternoon, while using Cursor, I encountered an issue where all my interactions with the AI (Chat or Agent) got stuck on ‘Planning next moves’ regardless of my input. I have verified that my network connection is functioning normally.

I checked the Cursor Developer Console and took a screenshot of the error logs (attached). The logs display an error suggesting that I need to be a ‘team member’ to access the resource (ConnectError: [unauthenticated] You must be a team member…).

However, I am currently a Pro plan subscriber, and my subscription is valid until June 2026. Could the official support team please explain why this error is occurring? I am currently unable to use Cursor at all because of this

Steps to Reproduce

Just talk to cursor IDE AI, it will be stuck on ‘Planning next moves’

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.21 (system setup)
VSCode Version: 1.105.1
Commit: 68e0a0385b87408d050869ea543e3778ad53f780
Date: 2026-01-02T23:46:13.381Z
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?

any model is the same issue

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like