Auto Agent Slow, Composer 2 as well

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Simple tasks seems to be taking an extra long time, while stuck on the first step after a prompt when agents are set to Auto. I switched to Opus and Sonnet 4.6 earlier in the day, but that eats through API usage. Now, Composer 2 also has the same behavior.

Steps to Reproduce

Stop prompt, change model, resubmit prompt

Expected Behavior

AI should assess and implement fixes quickly and efficiently.

Operating System

Windows 10/11

Version Information

Version: 3.2.16 (user setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto, Composer 2, Sonnet 4.6, Opus 4.6

For AI issues: add Request ID with privacy disabled

e9982063-e814-48b2-b38d-6e8d1a50775b

Additional Information

This has been ongoing throughout the day

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the report with the Request ID and version. This looks familiar, we’ve gotten a cluster of similar reports over the last few days about Auto/Composer 2 being slow:

From your request, we can see a short stall in the stream, but the request on the server finished without errors. This looks like latency, not throttling.

We’re already tracking a performance regression in agent chats internally, but we don’t have a clear ETA for a fix yet. If it gets better or worse after the next updates, let me know and I’ll update the thread.

Workarounds for now:

  • Cancel + resubmit when it hangs on the first step, like you did.
  • For long sessions, start a new chat once the context gets really large.