Stuck on "Taking longer than expected..." for multiple prompts

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Tasks get stuck in “Taking longer than expected…” and only progress if I edit the task and resend it.

This is preventing me from being able to queue up many actions and have cursor work through them.

Basically, after each task, it always gets stuck on the next one, going to “Taking longer than expected…” It will never resolve, it stayed like that for over 24 hours one time, I had to edit the prompt, and resend, then it basically works immediately.

This is really annoying.

Anyone else having this issue? is this a known problem? Restarting doesn’t seem to fix it, I’m out of ideas.

Steps to Reproduce

submit many prompts at once to a cursor agent

Expected Behavior

Cursor should be able to work through autonomously without needing my interaction

Operating System

Windows 10/11

Version Information

Version: 3.17.21 (user setup)
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @mgleeson_CDIT, thanks for the report!

This looks like an issue we’re tracking where a queued message can get stuck before it actually reaches the model, so the “Taking longer than expected” indicator just sits there indefinitely. Editing and resending pushes the message through again, which matches what you’re seeing.

Two things that would help us pin it down:

  1. When the next task gets stuck, is there still a copy of it in the queue tray, and does clicking “Send Now” on it push it through?
  2. If you can, grab a Request ID from a stuck chat (top-right chat menu, then Copy Request ID) and share it here.

In the meantime, “Send Now” on the queued item (when present) should also unstick it, alongside the edit-and-resend you found.