Planning next moves stuck

After submitting user input, the agent often says “Planning next actions,” animates the sentence, and does nothing at all. I don’t understand what happened. Have some limits been reached? Connection issues? Something else?

Sometimes the only thing that helps is restarting the entire Cursor IDE. But this might only work for one or two requests, after which the “Planning next actions” message reappears.

I tried automatic mode and Composer 1 — nothing helped :frowning: I switched from Pro to Pro+ with no result :frowning:

13 Likes
AI Agent Stuck on "Planning Next Moves" Infinitely – Affects All Models, No Error or Completion (Fresh Install, Diagnostics OK)
SLOW or NO response from the agent
Planning next moves - forever
Cursor response so slow?
Agent mode responding too slow, some time taking 15 minutes to respond
Agent unusable after update
Planning next moves for 5-10 minutes at a time!
Agent mode responding too slow, some time taking 15 minutes to respond
Agents are extremely slow to respond
Cursor runs very slowly and gets stuck on “Planning next moves
Cursor is unresponsive after sending a prompt to plan
Cursor IDE chat blocking in planning next move for few minutes
Cursor stops working - Connection Error
Agents not running at all
Agents are extremely slow to respond to generate code
Cursor has grinded to snail speed. A simple prompt takes 30 mins to run
Agents are extremely slow to respond to generate code
Agent with auto is freez all time and go in infinite loop
The cursor is running very slowly. Tasks that used to take 2 to 3 minutes to complete now often time out and feel laggy
Chat Frequently Stuck / Not Responding
Cursor stuck on simple commands like git commit etc
Models not working on 2.3.7
Models not working on 2.3.7
No Build button. Clicking on view plan does not opening it
IDE connected through SSH stuck on "Planning next moves"
Stuck in planning next move
Agent stuck in "Planning...", "Generating..."
Slow Context Summary, up to 10min wait
Agent hanging at Planning next moves due to Indexing
Window crashed when model generate plan with plan mode

Hi Aleksej,

This hanging on ‘Planning next actions’ often points to a connection or configuration conflict. Could you please check the following?

  1. Privacy Mode: Are you currently using Privacy Mode? If so, please try disabling it temporarily to see if that unblocks the agent.

  2. API Keys: Do you have a custom API key entered in the Cursor settings? If yes, please disable or remove it and try running solely on your Pro+ subscription. Sometimes custom keys conflict with the agentic capabilities.

  3. Fresh Context: Since restarting helps briefly, please try starting a completely New Chat (not just clearing the current one) combined with an IDE restart to rule out any corrupted session context.

1 Like

It’s happening to me all the time last two days, cursor became pretty much unusable now.

Nothing changed here and used to work perfectly.

You let it think for 3-5 minutes, then suddenly it works, sometimes does sometimes doesn’t. Then when you check it believed it thought for 5-11 seconds… Like ehhhh? Waited 5 minutes… Something is very wrong last couple of days.

10 Likes

It’s impossible to use! After a restart, the Cursor handles one or two requests (a little more for really light ones) and then it’s back to just gliding without moving. You restart it, and it loops around, if you’re lucky. Because if you’re unlucky, even after a restart you can’t achieve anything other than animated gliding into infinity. What’s going on? How do I use this? And this costs money? (Pro+)

And no, it’s not a context issue; context size doesn’t affect this behavior.

Either there are some priority queues (for a fresh launch), or the models are simply constantly overloaded. But something is clearly wrong, not on MY end.

4 Likes

I am having the same issue today…

Cursor just says ‘Planning next moves’ and never does anything. Worked once randomly.

Have been trying to resolve all morning

8 Likes

I didn’t use Privacy Mode.

I didn’t use API Keys.

The fresh context is not important, it does not depend on it.

And yes, I no longer use Cursor and have cancelled my subscription.

6 Likes

The same happens to me occasionally. Not every time, not on every chat, but every so often it will just get stuck and I either need to cancel and retry (and then it usually works) or it will just stop doing anything and then I need to ping the agent with “continue”

It’s really frustrating and it mainly happens with Composer, I hope Cursor team will address this. Even if the reason for this are temporary connection issues the agent should be smart enough to recognize this and keep retrying instead of getting stuck or failing silently.

2 Likes

how can i turn “Planning next moves” off? cursor is unusable because of it!!!

3 Likes

Is there a fix for this please? This is unbelievably infuriating. Cursor is literally unusable. Dead application. Cannot do ANYTHING. Please fix this ASAP. Not even worth holding the subscription at this point paying for an application that literally does not work anymore. Have tried all the suggested ‘fixes’ but absolutely nothing has changed, it’s completely unusable.

7 Likes

This is a completely unhelpful and mendacious response. It is broken, it was not broken in the past, and it will work better in the future. But this is useless to suggest and ignores the real issue. Maybe you’re not allowed to acknowledge this persistent ongoing issue, but in that case, I think it would vex the community less and do Cursor less harm to simply not reply at all instead of trying to gaslight us. It’s a regression, it’s very noticeable, and you are lying by omission by communicating otherwise then failing to follow-up.

I really think you should take some time off from “helping”, or speak with someone at Cursor about how to communicate better in the future. Unless this is a copy paste bot, in which case, the PM at cursor who proposed this should be moved away from a customer-facing product.

4 Likes

Hi everyone,

Quick check-in: There have been several updates released in rapid succession over the last few days aimed at improving stability and connection handling.

Is anyone still experiencing the Agent hanging on “Planning next actions” on the latest build, or has the behavior improved/resolved for you?

Please let us know if it’s running smoother now so we can confirm if the recent patches addressed the root cause.

1 Like

Hello,

I am experiencing the same issue: the app freezes during the planning stage and becomes unresponsive.

Here is what I have already tried to resolve the problem, without success:

  • Switching to HTTP/1.1 protocol.

  • Running the network diagnostic tool (result is green/“OK”).

  • Restarting the application.

  • Uninstalling and reinstalling the application.

During troubleshooting, I noticed that the app seems to be stuck in an infinite loop, specifically at the “codebase index” stage.

I have found one partial workaround: the AI agent does function if I open a very old chat session. However, this is not a viable solution, as those chats have overloaded and inefficient contexts.

2 Likes

Hi Duncan,

I appreciate the candid feedback. To be clear: I am not a bot, but a Community Ambassador volunteering to help fellow users here.

You are right—in hindsight, my previous suggestions regarding local settings (like API keys) were off the mark, given that this turned out to be a broader regression/backend issue. I apologize if that felt like gaslighting; my intention was to offer immediate troubleshooting steps while we waited for clarity on the server side.

I have flagged this thread some times ago. There have been several updates pushed in the last 72 hours specifically targeting these connection drops.

I hope the latest build resolves the issue for you. If not, I am here to help get those logs to the right people.

Hi Kostya,

Thanks for the detailed info.

Since we are seeing multiple similar reports coming in past few days (Yesterday/Today), I have forwarded this thread directly to the Cursor team so they can investigate what is going on.

I’d recommend holding off on further uninstalling/reinstalling for now until there is an official update or clarification from the team.

1 Like

Follow up:

I asked in Discord others and it seems that Planning Mode is functional:

Plan mode it’s fully working with 2.1.49

image

@Kostya_Arsk please update your Cursor IDE to the latest version.

I mentioned above that I had already tried reinstalling. About five minutes before writing, I installed the latest version from the website, but it didn’t help. I wrote the message after that. i try now again> v 2.1.49 - plan mode, agent mode, ask mode - not working.

I’ll restate the problem: it hangs indefinitely on “loading” the “codebase index,” while old chats work. The issue is obviously related to this—Cursor has started indexing unnecessary data and is clogging the channel. How can I disable indexing to test this theory?

keep this thread open; the issue is not resolved.

1 Like

Hi Kostya,

You’ve identified the core issue correctly — the infinite codebase indexing loop. This is a widespread bug in v2.1.47-2.1.49.

First, try this workaround that worked for another user last week:

  • Go to Cursor Settings → General ~ Privacy Mode → Toggle OFF

  • Then try a new Plan/Agent chat

  • Sometimes Privacy Mode interferes with indexing and causes these exact symptoms

If that doesn’t help, try these steps:

  1. Hard reset the index

    • Click “Delete Index” (visible in your Indexing & Docs panel)

    • Fully restart Cursor

    • Click “Sync” to rebuild

    • Test a new chat

  2. Reduce what gets indexed

    • Temporarily disable “Index New Folders” and “Index Repositories for Instant Grep”

    • Optimize .cursorignore (exclude node_modules/, .git/, dist/, build/, etc.)

    • Check if you’re hitting the file limit with

  3. Check the logs

    • Open View → Output → "Cursor Indexing & Retrieval"

    • Trigger Plan/Agent once, wait until it hangs

    • Share any errors or repeated messages you see

Why old chats work but new ones don’t:
Old chats use a cached index state. New chats try to load the current (never-finishing) index, which causes the freeze.

Please keep me in the loop and let me know if disabling Privacy Mode or any of these steps help!

Hi, I just got the new 2.1.50 update. Things are still bad.

  1. “Cursor Settings → General → Privacy Mode → Toggle OFF” — I always work in legacy mode, meaning data sharing is turned off.

  2. You mention “Hard reset the index”, but I don’t have a “Delete Index” button (visible in your Indexing & Docs panel). Maybe I’m looking in the wrong place. Please give more detailed instructions.

  3. “disable ‘Index New Folders’ and ‘Index Repositories for Instant Grep’” — I open a new Cursor window without any repositories, and it’s still indexing code. What is it indexing? This looks like a security leak.

  4. “View → Output → ‘Cursor Indexing & Retrieval’” — I don’t have the “Cursor Indexing & Retrieval” option.

1 Like

For me v 2.1.50 doesn’t help. Agent stuck on first request after launch. Cursor still not working for me at all.

5 Likes