Coding agent breaks after entering the plan mode

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since about a week, every single time I go into the plan mode, after I click Build the plan, the agent gets stuck with an infinite planning next move line, which at some point turns into a taking longer than expected one. In the end, it never gets to actually executing on the plan.

When I simply copy the content of the plan inserted into the original chat (meaning not even restarting the agent), it then picks up the execution as if nothing has happened. There is clearly something wrong with planning mode. I have updated the Cursor multiple times since I restarted the sessions, the agents, and so on. The bug still persists on the Mac OS MacBook Pro.

Steps to Reproduce

Plan a new feature in the plan mode and then press the build button. Give it some time and see that it doesn’t work.

Operating System

MacOS

Version Information

Version: 3.0.4 (Universal)
VSCode Version: 1.105.1
Date: 2026-04-02T09:36:23.265Z (3 days ago)
Layout: editor
Build Type: Stable
Release Track: Early Access
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

This is a known issue we’re actively tracking. The agent getting stuck specifically after clicking Build in Plan mode (while the plan itself generates fine) is a behavior pattern we’ve seen from other users as well.

Your workaround of copying the plan content back into the chat is actually the best approach for now. A couple of additional things to try:

  1. Request ID: The next time this happens, could you grab the Request ID? Click the three dots at the top right of the chat and select Copy Request ID, then share it here. This will help us trace what’s happening on our end during the stall. How to find your Request ID

  2. Which model are you using? The issue may behave differently across models. If you’re using Auto, try switching to a specific model (e.g., Claude 4.6 Sonnet) before clicking Build.

  3. Start a new conversation: If the agent gets stuck, starting a fresh chat (Cmd+N) and re-submitting your prompt directly (without Plan mode) can bypass the issue entirely.

Our team is aware of this and is working on it. The Request ID from a stuck Build attempt will help us narrow down the specific failure point.