Cursor gets stuck indefinitely on tasks, requiring manual intervention

Describe the Bug

Cursor hangs for extended periods (potentially hours) during task execution, showing “Planning next moves” or similar status indefinitely until manually interrupted. Issue is not model-specific (affects both Claude and OpenAI models).

Impact: High - significantly impacts developer productivity

Symptoms:

  • Tasks hang indefinitely with no progress
  • Eventually times out with “Connection failed” error
  • Affects multiple users across the organization

Workarounds reported:

  1. Restart laptop (worked for some)
  2. Delete/move ~/.cursor directory (nuclear option, worked for others)

Suspected cause:
Possible proxy-level or local network issue causing streaming HTTP responses from LLMs to fail.

Environment:

  • Started appearing ~Dec 12, 2025
  • May be related to Cursor update (one user noted they hadn’t updated and weren’t affected)

Affected users: Multiple (Ford Prior, Stephen Gross, James Ainslie, others)

Steps to Reproduce

  1. Open Cursor IDE
  2. Initiate any AI task (Composer, inline edit, chat, etc.)
  3. Observe task entering “Planning next moves” or similar processing state
  4. Task hangs indefinitely with no progress or output

Reproduction notes:

  • Intermittent - does not occur on every task
  • Not reliably reproducible on demand
  • Appears to happen more frequently after Cursor update
  • May be triggered by network/proxy conditions (streaming HTTP response failure suspected)
  • Model-agnostic (Claude, GPT-4, GPT-5.2 all affected)

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
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

Sometimes - I can sometimes use Cursor

Hi Ford!

I can see that you’re on the Enterprise plan. The best way to get support is to reach out directly at [email protected]. Our Support Engineers can handle these issues confidentially and with a bit more reactivity than you’ll likely get from a community forum.