Performance Regression: Plans Stuck in Pending State Since 2.3.14

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Response speed was excellent in version 2.3.14, but has significantly degraded in the latest version. Constantly waiting on pending plans - Plan Mode appears to get stuck or takes an extremely long time to generate plans, leaving plans in a perpetual “pending” state. Overall agent responses and editor performance are noticeably slower.

Steps to Reproduce

  1. Use Cursor version 2.3.14 (excellent performance)
  2. Upgrade to latest version
  3. Attempt to use Plan Mode or agent features
  4. Observe plans getting stuck in “pending” state for extended periods or indefinitely
  5. Experience slower response times in agent interactions and general editor responsiveness

Expected Behavior

Response times should match or exceed the performance experienced in version 2.3.14, which had excellent response speed. Plans should generate promptly without getting stuck in pending state.

Operating System

Windows 10/11

Version Information

Version: 2.3.14 (system setup)
VSCode Version: 1.105.1
Commit: b3e9fe6c37659159fc2dec9ae643d74c25e5d0d0
Date: 2025-12-29T23:26:25.365Z
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

and
latest version 2.5+

For AI issues: which model did you use?

Multiple models enabled: Composer 1.5, Opus 4.6, Sonnet 4.6, GPT-5.3 Codex, GPT-5.2. Issue occurs across all models when using Plan Mode.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. A couple things that’ll help narrow this down:

  1. What exact version are you on? You mentioned 2.5+, it’d help to share the specific version from Help > About.

  2. When the plan gets stuck in “pending”, does it eventually finish, or does it stay there forever? Does starting a new chat help?

  3. Can you grab the Request ID for the stuck plan? Click the three dots in the top-right of the chat > Copy Request ID.

  4. Please run the network diagnostics: Cursor Settings > Network > Run Diagnostics, then share the results.

  5. Quick check: try running with extensions disabled by running cursor --disable-extensions in the terminal. If Plan Mode works fine after that, it’s likely an extension conflict.

Earlier Plan Mode performance issues were fixed in older versions, but what you’re seeing on 2.5+ could be a new regression or something specific to your setup. The diagnostics above should help us figure out what’s going on.

4

I would like to withdraw this bug as I feel it might be on my end that issue is occuring will delve deeper into the issue and give a better response

1 Like
5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.