Cursor Models are not giving any response

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have cursor pro plan ($20) which I bought on 12th September. Since yesterday, when I am asking anything to cursor agent, it is showing - taking longer than expected. How to resolve this? I have already closed and reopened the IDE but same issue is appearing again.

Steps to Reproduce

Open cursor IDE and open agent window then ask anything. It will start showing - taking longer than expected.

Expected Behavior

It should give response/answer to asked problem.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Cursor IDE Latest version

For AI issues: which model did you use?

Grok 4.6/4.7, Claude Opus 5.5

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Sandeep_Kumar1,

This isn’t anything on your end. Your plan, account, and network are all fine. It’s a client-side issue on Windows in the current version where the request gets stuck inside the app before it’s sent, so it sits on “Taking longer than expected.” Not intended behavior, and it’s an issue we’re tracking.

To get unstuck in the meantime:

  1. Before sending, close any open file tabs (Ctrl+W, or click the × on the tab). The hang is tied to having a file open as the active editor, so sending with none active usually goes through.
  2. If it’s still stuck, run “Developer: Reload Window” from the Command Palette (Ctrl+Shift+P), wait ~30s, then try again.
  3. The separate Agents window is usually unaffected as a fallback.

I’ll post an update here. Let me know if none of these help.

Update: This is now working for me. Thanks!

Still happening on my end as well. I’ve tried a few different troubleshooting steps without success:

  • Reinstalled Cursor: Downloaded and ran the latest installer.

  • Hard Quit: Completely quit and restarted the application.

Despite these steps, the issue persists across multiple models (including Grok 4.7, Grok 4.6, and various Claude models)—they either fail to give a response or get hung up loading indefinitely.

Temporary Workaround: For now, I’m using the separate Agent / Composer window, which seems to be working as expected.