Planning next moves for 5-10 minutes at a time!

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever the models go to planning next moves they get stuck for about 5-10 minutes at a time

Steps to Reproduce

Use Gemini or Anthropic models.

Expected Behavior

Only go to planning next moves for 1 minute max.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

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

For AI issues: which model did you use?

All of the Anthropic and Google models. Composer 1 is fine.

Additional Information

It will implement the code quickly, but the "planning next moves"part between code implementations is just incredibly slow.

I’ve tried disabling all my mcp’s, creating a new project. Disabling all my rules. My network diagnostics look completely fine. There’s something going on between Cursor and the model providers.

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report.

This matches an ongoing investigation. We need some data to link your case:

Please send:

  • 2-3 Request IDs from the stuck messages with Anthropic/Google (message menu in chat > Copy Request ID): Getting a Request ID | Cursor Docs
  • A screenshot of Settings > Network > Run Diagnostics
  • A screenshot of Indexing status for your project and for an empty folder
  • Errors from Help > Toggle Developer Tools > Console while it’s stuck

Quick checks:

  • Settings > search for HTTP/2 > enable Disable HTTP/2, restart and test. If it didn’t help, disable it back and test again
  • Run without extensions: in terminal run cursor --disable-extensions, open an empty folder, and test the agent
  • Temporarily disable MCP if enabled
  • Test on another connection without VPN/proxy (for example, a mobile hotspot)

Related threads with progress and workarounds:

Send the data above, I’ll add it to the investigation and follow up with an update.

A post was merged into an existing topic: All models respond too slowly

A post was merged into an existing topic: Planning next moves stuck