# Performance Issues - can't work

**URL:** <https://forum.cursor.com/t/performance-issues-cant-work/156402>\
**Category:** Bug Reports\
**Tags:** performance, composer\
**Created:** [April 1, 2026, 11:08am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402 "2026-04-01T11:08:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chriskk](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@Chriskk](https://forum.cursor.com/u/Chriskk)\
**Post date:** [April 1, 2026, 11:08am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/1 "2026-04-01T11:08:51Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

I have been experiencing significant issues with Cursor AI for about a week now. I primarily use Composer 2.0 to work on my project, but it has become almost unusable.

Even when I ask it to perform a very small task, I constantly see messages like “Taking longer than expected etc.” The performance is extremely unstable and slow, making it impossible to maintain a professional workflow.

I am a Pro+ subscriber, yet the program is currently not fit for purpose, and I am being forced to use competitors’ tools to get my work done.

I have already checked my network diagnostics (which are successful) and tried re-indexing my codebase, but the issue persists. Please help me resolve this as soon as possible.

### Steps to Reproduce

Open a project with around 1500 files.

Open Composer 2.0 (Cmd+I / Ctrl+I).

Select any model (e.g., Claude 3.5 Sonnet or GPT-4o).

Provide a simple prompt for a small change in the code.

Observed result: The generation hangs, and a “Taking longer than expected” message appears. The process is extremely slow or fails to complete, despite having a Pro+ subscription and a healthy network connection.

This happens consistently across different small tasks within the project.

### Operating System

MacOS

### Version Information

Version: 2.6.22

### For AI issues: which model did you use?

Composer 2

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 1, 2026, 11:24am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/5 "2026-04-01T11:24:04Z")

</div>

Hey, thanks for the report. This is a known issue, and we’re seeing similar reports from other users.

For debugging, we need the Request ID from one of the stuck requests. Here’s how to get it:

- Create a new chat and send any prompt via Composer 2
- When the response finally comes back or gets stuck, click the chat menu in the top right, then select Copy Request ID
- Paste it here

Also try this workaround: open settings with `Cmd+,` search for HTTP/2, and turn on Disable HTTP/2. Then restart Cursor. In some cases, this fixes delay issues.

The team is aware of this issue. The Request ID will help us narrow down what’s happening in your specific case.

---

<div class="post-metadata">

**Author:** ![Chriskk](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@Chriskk](https://forum.cursor.com/u/Chriskk)\
**Post date:** [April 1, 2026, 11:32am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/7 "2026-04-01T11:32:08Z")

</div>

e1d6dfa4-3aef-4f8c-8144-dc408a2896ff

Switched to http 1.1 but it didn’t gives me any improve/progress.

---

<div class="post-metadata">

**Author:** ![Patrick\_Cook](https://avatars.discourse-cdn.com/v4/letter/p/7ea924/32.png) [@Patrick\_Cook](https://forum.cursor.com/u/Patrick_Cook)\
**Post date:** [April 1, 2026, 5:57pm UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/8 "2026-04-01T17:57:14Z")

</div>

I am also having the same issues. Tasks that used to be lighting quick take 10 minutes+ now. And ive switched back to Composer 1.5 and same issue. For the cost of the Pro+ subscription, this is ridiculous. It complete ruins the flow of development. And since AI often hallucinates the wrong solution, fast iteration is imperative. But due the extreme slowness over the last few weeks, iterating is painful and often i wonder if I could just write the code faster my self. And Im not trying to be dramatic, truly, i could do a lot of this with higher accuracy and speed when you account for how many iterations it takes to complete a task.

Request ID: 02a7a6aa-4cea-4367-ab02-7a215f85d40c

---

<div class="post-metadata">

**Author:** ![Chriskk](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@Chriskk](https://forum.cursor.com/u/Chriskk)\
**Post date:** [April 2, 2026, 9:07am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/12 "2026-04-02T09:07:08Z")

</div>

I‘ve switched model from composer 2 to opus. Works much better. Composer worked very well after releasing, efficiency of that model is not acceptable now..

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 2, 2026, 9:57am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/14 "2026-04-02T09:57:08Z")

</div>

Glad switching to Opus helped. That’s a good workaround for now. Composer 2 is currently seeing latency issues, and the team is aware.

@Patrick_Cook, try the same workaround. Switch to a different model like Opus or Claude 4.5 Sonnet instead of Composer 2 until this is fixed.

Let us know if anything changes.

---

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [April 7, 2026, 9:56am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/16 "2026-04-07T09:56:37Z")

</div>

Hey @Chriskk, @Patrick_Cook, @_gf!

The chat hanging / ‘Taking longer than expected’ issue has been addressed in a recent Cursor update. Updating to the latest version should resolve this.

---

<div class="post-metadata">

**Author:** ![Chriskk](https://avatars.discourse-cdn.com/v4/letter/c/eb8c5e/32.png) [@Chriskk](https://forum.cursor.com/u/Chriskk)\
**Post date:** [April 10, 2026, 9:36am UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/17 "2026-04-10T09:36:56Z")

</div>

Much better. Thanks.

---

<div class="post-metadata">

**Author:** ![master3395](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/master3395/32/46687_2.png) [@master3395](https://forum.cursor.com/u/master3395)\
**Post date:** [April 10, 2026, 12:39pm UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/18 "2026-04-10T12:39:12Z")

</div>

Didn’t help.

> [@Cursor is unusable, extremely slow since this morning](https://forum.cursor.com/t/cursor-is-unusable-extremely-slow-since-this-morning/156674/10):
>
> I had to downgrade to CursorSetup-x64-2.6.22.exe in order to make it run faster. 3.x was way too slow!

---

<div class="post-metadata">

**Author:** ![Aaron\_Raven](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Aaron\_Raven](https://forum.cursor.com/u/Aaron_Raven)\
**Post date:** [April 11, 2026, 7:16pm UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/19 "2026-04-11T19:16:35Z")

</div>

Hello  
Same issue here, Cursor is up to date (v3.0.16), but is hagging with “taking longer than expected…”  
id : dd5cda0d-5e08-4f8c-b2fc-0cb9fceffb70

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [May 3, 2026, 7:16pm UTC](https://forum.cursor.com/t/performance-issues-cant-work/156402/20 "2026-05-03T19:16:55Z")

</div>

Closed on May 3, 2026, 7:16pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.
