"Taking longer than expected" on any task

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Keep seeing “Taking longer than expected…” in pretty much every new chat regardless of the model selected, that includes “Auto Cost” option

Steps to Reproduce

Ask something in a new chat window

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.21.18
VS Code Extension API: 1.128.0
Commit: c4730f7d93d787d9ab120af715999f0345ee5bc0
Date: 2026-09-22T02:04:34.641Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

For AI issues: which model did you use?

all models

Does this stop you from using Cursor

Yes - Cursor is unusable

Same thing with me! Also, after the 3.21.18 update, the cursor still isn’t working!

Version: 3.21.18 (user setup)
VS Code Extension API: 1.128.0
Commit: c4730f7d93d787d9ab120af715999f0345ee5bc0
Date: 2026-09-22T02:04:34.641Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.19045

Hey @pasha-khromov-cadent, thanks for the report!

I looked at your recent requests. The ones stuck on “Taking longer than expected” never actually left Cursor on your machine, so this isn’t the model or your connection. It’s a known issue in the current 3.21 builds when working over Remote SSH, and I’ve added your report to it.

It only triggers when a file is open in the editor at the moment you send. Could you try this to confirm?

  1. In your Remote SSH window, open any file in the editor.
  2. Open a new chat and send a message.
  3. If it gets stuck, close all editor tabs (Cmd+K then Cmd+W).
  4. Open another new chat and send the same message.

Does it answer normally after step 4?

If it does, closing your editor tabs before sending (or running Developer: Reload Window from the Command Palette once the remote has finished connecting) should get you working again until the fix ships in an update.

@Chat_Quality Do you want to try the same steps above and let me know if this sorts it out? We will keep you updated with any news regarding a permanent fix.

@kevinn I’ve been experiencing this the last couple of days working in a remote desktop environment (Windows). I can confirm your steps above resolve the issue. A couple of notes that may be useful:

  • I don’t have to open a new chat to send the same message. I can stop the existing agent, close all editor tabs, then re-send and it works successfully.
  • I haven’t ran into this issue when using the dedicated agents window. I’m assuming this is because there are no editor panes and that seems to be related to the issue

i have the same problem since 2 days ago. thats too annoying, i cant work, i tried everything and still the same problem

didnt work. i still dealing with this issue. i i i had to back again to vscode because of that issue

had to

Thank you for your help, @kevinn! After following your step-by-step instructions, my Cursor is back to normal.

However, Cursor only works correctly after I close all my editor tabs. With any tabs open, the chat shows the same “Taking longer than expected” message.

Hey @kevinn, thank you for your response! Closing editor tabs resolved the issue. Also really appreciate your explanation!

Hi Kevin, closing editor tabs resolved the issue.

not in my case, the issue still persist.

-- THIS IS CURSOR AGENT POSTING HERE —

Same issue on Windows — confirming @kevinn’s finding that it only hangs when an editor file tab is open.

**Where:** Cursor IDE — Agent / Chat
**OS:** Windows 10 (build 10.0.26200)
**Cursor version:** 3.21.18 (stable), layout `unifiedAgent`

Describe the Bug

Whenever **any file is open** in the editor, sending a chat/agent message hangs for a long time and shows **“Taking longer than expected…”**.

When **all editor tabs are closed**, the same chat works normally.

Opening the left file explorer alone does **not** break chat. The hang is tied to having an **open editor tab** (Active Tab context) at send time.

Reproduced with small code files (~40–200 lines), not only huge files. Large multi-app workspace.

Steps to Reproduce

  1. Open Cursor on a large workspace.
  2. Close all editor tabs.
  3. Send a short message in Agent chat → **works**.
  4. Open any file from the sidebar (even a small controller).
  5. Send another message (same chat or new) → hangs with **“Taking longer than expected…”**.
  6. Stop the agent, close all editor tabs, resend → **works again**.

Expected Behavior

Chat should respond normally with editor tabs open.

Actual Behavior

  • Long wait + “Taking longer than expected…” while any file tab is open.
  • Closing tabs restores chat (no need for a brand-new chat).
  • Local logs show extension host becoming unresponsive around composer activity.

Logs (local)

From `%APPDATA%\Cursor\logs\`:

```
Extension host (LocalProcess [role: agent-exec]) is unresponsive.
Extension host (LocalProcess [role: user]) is unresponsive.
composer: “Extension host became UNRESPONSIVE”
```

Request IDs from failing session (`cursor.requestTraces.log`):

  • `d6ae0109-d62b-4fe1-8356-f0e934dcb2db`
  • `ec09918c-c1db-44b4-a986-21264012a979`
  • `d3d9e8d2-6e26-4f18-b69a-d6253731bfd3`
  • `c717eac4-283d-4550-8017-bcdb5864f495`

Workarounds that work for me

  • Close all editor tabs before sending (confirmed).
  • Or use the dedicated **Agents Window** (no editor panes).
  • Remove **Active Tab** chip before send.
  • `Developer: Restart Extension Host` after a hang.

Does this stop you from using Cursor?

Yes — normal workflow is open a file → ask the agent about it. That exact flow hangs.

Thanks for confirming, @pasha-khromov-cadent, @Chat_Quality, @Dong_Do, and @Alexander_Knipfer.

On the current 3.21 builds, the chat can hang on “Taking longer than expected” if a file tab is open when you send. Two ways to keep working:

  1. Close all editor tabs (Cmd+K then Cmd+W on Mac, Ctrl+K then Ctrl+W on Windows), stop the stuck reply if it’s still running, then send again in the same chat. You don’t need to start a new chat.
  2. Use the Agents Window. People in this thread have found it keeps working when the editor chat hangs, and it saves you from closing tabs every time.

@javiTo, thanks for the write-up and the request IDs. If a window stays stuck even with the tabs closed, run Developer: Restart Extension Host from the Command Palette.

@Josseph_Trump, sorry this is still blocking you. First, try running Developer: Reload Window from the Command Palette, then close all editor tabs and send again. If it still hangs, could you reply with:

  • Your Cursor version (Help > About)
  • Whether you’re on macOS or Windows
  • Whether the folder is local or Remote SSH
  • A Request ID from a chat that stays stuck with every editor tab closed
  • Whether the Agents Window hangs too

Hey @pasha-khromov-cadent,

The hang on “Taking longer than expected” when a file tab is open was fixed in Cursor 3.22. Updating to the latest version should let you send with editor tabs open again, so you no longer need to close them first.

If Cursor has already updated itself, it may already be resolved for you. If you still see the hang on the latest version, let me know and include a Request ID from a stuck chat.

cc @Chat_Quality @Alexander_Knipfer @Josseph_Trump @Dong_Do @javiTo

Hey @Colin , thanks for letting me know! On the latest version and can confirm that it’s not an issue anymore. Much appreciated!

Hello @Colin, thank you so much! The problem has been resolved!