Planning next moves getting longer and longer - now up to 8 minutes

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

As has been mentioned many times in the mega thread, since December, Planning next moves… has been 1-3 minutes after every single request.

Now, it just sits there forever.

Looking at the developer tools, I see this every time:

workbench.desktop.main.js:13688 [composer] No first token received within 2s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 4s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 6s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 8s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 10s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 12s
Object
workbench.desktop.main.js:13688 [transport] Connect error in unary AI connect ConnectError: [unauthenticated] You must be a team member to access this resource
at t (workbench.desktop.main.js:12706:476909)
at async Object.getTeamCommands (workbench.desktop.main.js:566:27065)
at async L9o.loadTeamCommands (workbench.desktop.main.js:15682:3633)
Object
workbench.desktop.main.js:15682 Failed to load team commands: ConnectError: [unauthenticated] You must be a team member to access this resource
at t (workbench.desktop.main.js:12706:476909)
at async Object.getTeamCommands (workbench.desktop.main.js:566:27065)
at async L9o.loadTeamCommands (workbench.desktop.main.js:15682:3633)
workbench.desktop.main.js:13688 [composer] No first token received within 14s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 16s
Object
workbench.desktop.main.js:13688 [composer] No first token received within 32s
Object

No activity on the network pane.

Steps to Reproduce

Ask an agent anything in the conversation.

Planning next moves…

Expected Behavior

The agent will do something.

Screenshots / Screen Recordings

Screenshot 2026-02-12 160603.png
Screenshot 2026-02-12 160603.png396×202 5.04 KB

Operating System

Windows 10/11

Version Information

Version: 2.3.35 (system setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
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?

Auto, Composer 1.5, GPT 5, any of them. Doesn’t make a difference.

For AI issues: add Request ID with privacy disabled

“31f07a15-6881-4030-bc41-eeec49577798”

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. A couple of things.

First, you’re on version 2.3.35, which is pretty old. Since then we’ve shipped a few fixes for getting stuck on “Planning next moves” (including better timeout handling and provider responsiveness). Please update to the latest version.

Second, the console error [unauthenticated] You must be a team member to access this resource is a separate issue. It usually means your auth session has expired. Please try this:

Also worth trying:

  • Cursor Settings > Network > Run Diagnostics to confirm there are no connection issues
  • If you have any MCP servers configured, check if any are in an error state and temporarily disable them

If the issue still happens after updating and re-authing, share the new version info and a fresh Request ID and we’ll take a look.

4

I am on version 2.3 because one of the posts on here suggests downgrading to 2.3 as a fix for this problem. It did not help.

5

All extensions removed. No MCPs. No change.

6

Run diagnostics shows no problems.

No change to the problem whether I’m on http 2 or 1.1

7

My whole dev team is seeing the same problem. We’ve been installing the latest version eagerly every time they come out, hoping that cursor is usable again. But we’ve been disappointed since December. It’s just getting worse and worse.

8

Noticing the bug reports pile up in here for the same problem. And get dismissed by the cursor team with the same suggestions over and over that everyone reports don’t work.

10

We’ve now stopped our cursor evangelizing, because we go to show it off, but a flashing Planning next moves is not an impressive demonstration.

11

What is needed is a verbosity flag to output more debug info to the developer tools console, so that we can see exactly what it is getting stuck on.

In the developer tools console, clicking on that file link doesn’t show anything. The file doesn’t load.

12

image
image1683×390 46.6 KB

13

“34242a8a-a460-40c2-a2ec-8a2fb9a3b2a0”

14

Might be relevant:

  • Response time in the office, with the codebase on a shared network drive - 1-3 minutes.

  • Response time at home, over VPN, with the codebase on a shared network drive - 8+ minutes.

These times are very reliable. Prior to November, response time was 1-5 seconds.