Composer 2 Fast

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

New chat and use composer 2 fast model, it will always load for a long long time to answer. I attached a screenshot, I just greet hey and it took 62s to answer. But after the first prompt in the new chat, it will function normally.

Steps to Reproduce

Create a new chat and use Composer 2 Fast model, simply just prompt anything you like.

Expected Behavior

New chat will not face this issue?

Screenshots / Screen Recordings

Screenshot 2026-03-26 180816.png
Screenshot 2026-03-26 180816.png417×966 12.1 KB

Operating System

Windows 10/11

Version Information

Version: 2.6.21 (system setup)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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?

Composer 2 Fast

Additional Information

Composer 2 without Fast works fine.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, I see the screenshot. 62 seconds for “hey” is definitely not normal for Composer 2 Fast.

To debug this, we need the Request ID from the slow first prompt. To get it:

  • Create a new chat, send anything using Composer 2 Fast
  • When the reply finally comes back, open the chat menu in the top right corner and select Copy Request ID
  • Paste it here

Also try one workaround. Open App Settings with Ctrl+,, find HTTP/2, and turn on Disable HTTP/2. Restart Cursor and see if anything changes. Sometimes network quirks can cause these delays on the first connection.

Let me know how it goes.

1 Like
6

this is the Request ID: a176d0b1-836f-481b-92d9-f566ffb8af93
Yea thank you very much Dean Rie, I disable HTTP/2 and now it works fine :+1: . I tried 5 new chat and it response instantly.

1 Like
7

Glad it helped! I’m marking this topic as resolved.

I saved the Request ID in case we need it for further troubleshooting. If the issue comes back, let me know.

1 Like