Composer 2 & Auto - 'Planning Next Moves' or 'Taking longer than expected' hang/freeze

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

About 3~ hours or so ago in the Cursor IDE, all Composer 2 agents (and ‘Auto’ mode) have starting hanging with ‘Taking longer than expected’ or ‘Planning Next Moves’ and they never respond/answer.

Composer 2 was working fine earlier today but now I’m experiencing this issue and starting new chats, restarting, etc… no change.

Steps to Reproduce

Ask the agent to perform any task.

Expected Behavior

A response/action from the agent

Operating System

Windows 10/11

Version Information

Version: 3.0.16 (user setup)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Composer 2

For AI issues: add Request ID with privacy disabled

878da60f-38d1-4c44-bbcf-6240b24a45fe

Does this stop you from using Cursor

Yes - Cursor is unusable

2 Likes

Same for me.

Yep- wasted the last three hours trying every suggestion on this forum to fix it.

Auto and Composer 2 execute 1 or 2 steps and then hang with ‘Planning Next Moves’ or ‘Taking longer than expected’.

Other models work so this seems specific to Auto mode and Composer 2.

Same I also stuck without any resolution

Hey, thanks for the detailed report and the Request ID.

Confirmed, there are infra issues right now affecting Composer 2 and Auto mode. It’s not on your side, this is impacting many users.

Until things stabilize, you can try a workaround: manually pick a specific model like Claude Opus 4.6 or another one instead of Auto or Composer 2. A few users in this thread confirmed it unblocked them: Taking longer than expected on Cursor version 3.0.13 - #22 by Garrett_Giles

The team is aware. Let me know if the workaround helps.

1 Like