# Composer 2.5 extremely slow after Cursor client update; switching models only temporarily helps **URL:** \ **Category:** Bug Reports\ **Tags:** performance, composer, chat\ **Created:** [August 4, 2026, 3:25am UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376 "2026-08-04T03:25:00Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cong](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cong/32/115616_2.png) [@cong](https://forum.cursor.com/u/cong)\ **Post date:** [August 4, 2026, 3:25am UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/1 "2026-08-04T03:25:00Z")
I’ve been using **Composer 2.5** exclusively. After updating the Cursor client, chats with this model became extremely slow/unresponsive. I waited over **7 minutes** and still got no output (no fix plan or response). Switching to another model (e.g. **Auto** ) restored normal speed. However, switching back to **Composer 2.5** in the same session made responses slow again. Starting a **new chat** did not fix the issue either. Version: 3.14.7 (system setup) VS Code Extension API: 1.128.0 Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0 Date: 2026-07-30T06:41:34.009Z Layout: IDE 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.19045 ---
**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:** [August 4, 2026, 3:25am UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/2 "2026-08-04T03:25:09Z")
Hi there! We detected that this may be a bug report, so we’ve moved your post to the **Bug Reports** category. To help us investigate and fix this faster, could you edit your original post to include the details from the template below? > **Bug Report Template - Click to expand** > > **Where does the bug appear (feature/product)?** > > - Editor, Tab & Chat (autocomplete, Composer, in-editor agent) > - Terminal & commands > - Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock) > - MCP & tools > - Cloud Agents & Automations ([cursor.com/agents](http://cursor.com/agents), scheduled/event) > - BugBot & Code Review > - Cursor CLI > - Cursor Mobile > - Remote (SSH / Dev Containers / WSL) > - Account, billing & login > - Something else… > > * * * > > **Describe the Bug** > A clear and concise description of what the bug is. > > * * * > > **Steps to Reproduce** > How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them! > > 1. … > 2. … > 3. … > > * * * > > **Expected Behavior** > What is meant to happen here that isn’t working correctly? > > * * * > > **Screenshots / Screen Recordings** > If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov) > > * * * > > **Operating System** > > - Windows 10/11 > - MacOS > - Linux > > * * * > > **Version Information** > > - For Cursor IDE: Menu → About Cursor → Copy > - For Cursor CLI: Run `agent about` in your terminal > > ```auto > IDE: > Version: 2.xx.x > VSCode Version: 1.105.1 > Commit: ...... > > CLI: > CLI Version 2026.01.17-d239e66 > > ``` > > * * * > > **For AI issues: which model did you use?** > Model name (e.g., Sonnet 4, Tab…) > > * * * > > **For AI issues: add Request ID with privacy disabled** > Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1 > For Background Agent issues, also post the ID: bc-… > > * * * > > **Additional Information** > Add any other context about the problem here. > > * * * > > **Does this stop you from using Cursor?** > > - Yes - Cursor is unusable > - Sometimes - I can sometimes use Cursor > - No - Cursor works, but with this issue The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks! ---
**Author:** ![yaireo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/yaireo/32/4017_2.png) [@yaireo](https://forum.cursor.com/u/yaireo)\ **Post date:** [August 4, 2026, 6:48am UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/5 "2026-08-04T06:48:51Z")
Also for me since yesterday extremely slow. Also Grok 4.5. Even on “fast” mode they are both slow. This started as of sometime yesterday (August 3) ---
**Author:** ![cong](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cong/32/115616_2.png) [@cong](https://forum.cursor.com/u/cong)\ **Post date:** [August 4, 2026, 6:56am UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/6 "2026-08-04T06:56:11Z")
This issue frequently occurs after a client upgrade, but it’s unclear whether it’s a bug. ---
**Author:** ![ter\_ry](https://avatars.discourse-cdn.com/v4/letter/t/35a633/32.png) [@ter\_ry](https://forum.cursor.com/u/ter_ry)\ **Post date:** [August 4, 2026, 1:11pm UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/7 "2026-08-04T13:11:08Z")
I encountered this issue yesterday as well, and it still persists. ---
**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:** [November 2, 2026, 1:12pm UTC](https://forum.cursor.com/t/composer-2-5-extremely-slow-after-cursor-client-update-switching-models-only-temporarily-helps/167376/8 "2026-11-02T13:12:01Z")
Closed on November 2, 2026, 1:12pm UTC This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.