Cursor version issue

Support Bug Reports
1

I updated to the latest Cursor version (Version: 3.21.18), and now I often get a “taking longer than expected…” message, and then it just stays there and doesn’t work. When I switch back to the previous version 3.20.21, there is no such problem. What is going on? It has gotten to the point where I don’t even dare to update anymore.

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)

Describe the Bug
After updating to Cursor 3.21.18, Agent/Chat frequently shows “taking longer than expected…” and then hangs indefinitely with no response. Rolling back to 3.20.21 makes the problem go away. The regression is severe enough that I no longer feel safe updating.

Steps to Reproduce

  1. Update Cursor to version 3.21.18.
  2. Open Agent / Chat and send a normal request.
  3. Observe the “taking longer than expected…” message; the request then stays stuck and never completes.
  4. Roll back to 3.20.21 and repeat the same workflow — it works normally.

Expected Behavior
Agent/Chat should respond normally on 3.21.18 the same way it does on 3.20.21, without hanging after “taking longer than expected…”.

Screenshots / Screen Recordings
N/A for now (can attach if needed).

Operating System

  • Windows 10/11

Details: Microsoft Windows 11 Pro, Version 10.0.22631, 64-bit

Version Information
Currently installed (rolled back, working):

Broken version: 3.21.18 (same machine; downgraded after the hang started)

For AI issues: which model did you use?
Various / default Agent models (issue appears across sessions on 3.21.18)

For AI issues: add Request ID with privacy disabled
Not captured yet; happy to provide one if I hit the issue again on 3.21.18.

Additional Information

  • Install path on this machine: D:\cursor
  • Problem only appears after updating to 3.21.18; 3.20.21 is stable on the same machine and workflow.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable (on 3.21.18; usable again after rollback to 3.20.21)
2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

7

Updated

9

Hey @tang_wang,

This isn’t anything in your setup. It’s an issue we’re tracking on Windows with the 3.21 builds, where a request can get stuck on your machine before it’s ever sent, so it just sits on “Taking longer than expected…”. Staying on 3.20.21 is completely fine in the meantime, so no need to feel stuck about updating.

If you do want to be on 3.21, two things clear it for most people: fully quit and reopen Cursor (not just reload the window), or send from the separate Agents window, which isn’t affected.

I’ll post here when there’s an update.

11

I’m experiencing this issue on MacOS 26.5.1. Does switching to HTTP/1.1 help?

12

I’m not sure about Mac, but on the Windows version, I’ve tried switching to HTTP/1.1, and it didn’t really help.

14

Hey @tang_wang,

The issue where Agent/Chat got stuck on “Taking longer than expected…” after updating to 3.21 has been fixed in a recent Cursor update (3.23)

It may already be resolved on your current version, so it’s worth a quick check. If you’re on the latest version and still seeing the hang, let me know and we’ll take another look.

Thanks for the report!

cc @eshaggy82