# Agents are extremely slow to respond

**URL:** <https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032>\
**Category:** Bug Reports\
**Created:** [December 12, 2025, 5:44am UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032 "2025-12-12T05:44:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Z\_W](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/z_w/32/86058_2.png) [@Z\_W](https://forum.cursor.com/u/Z_W)\
**Post date:** [December 12, 2025, 5:44am UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/1 "2025-12-12T05:44:41Z")

</div>

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

Cursor IDE

### Describe the Bug

Today, when using Cursor, all agents were extremely slow to respond. Each message took approximately 3–5 minutes to get a response.

What’s unusual is that the system was not completely frozen. After waiting for a long time, the agents would eventually respond, but the delay was consistently very long.

### Steps to Reproduce

Use agents

### Expected Behavior

Agents should respond within a normal, reasonable time frame.

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.17  
VSCode Version: 1.105.1  
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70  
Date: 2025-12-11T18:30:06.649Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Darwin arm64 24.4.0

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

Opus 4.5 thinking, Opus 4.5, composer 1, codex max

### For AI issues: add Request ID with privacy disabled

f10cad29-3cfa-4a4e-a358-ebb356ed0cee

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**Author:** ![sanjeed5](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sanjeed5/32/9610_2.png) [@sanjeed5](https://forum.cursor.com/u/sanjeed5)\
**Post date:** [December 12, 2025, 1:46pm UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/2 "2025-12-12T13:46:03Z")

</div>

Split this topic on December 12, 2025, 1:46pm UTC

4 posts were merged into an existing topic: [Planning next moves stuck](https://forum.cursor.com/t/planning-next-moves-stuck/143985)

---

<div class="post-metadata">

**Author:** ![sanjeed5](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sanjeed5/32/9610_2.png) [@sanjeed5](https://forum.cursor.com/u/sanjeed5)\
**Post date:** [December 12, 2025, 1:45pm UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/5 "2025-12-12T13:45:36Z")

</div>

Thanks for the detailed report. This matches the widespread agent slowness issue affecting multiple users. Your worktree finding is helpful. I’ll merge this with similar reports and share it with the team to help them investigate.

---

<div class="post-metadata">

**Author:** ![aaaaaaaaaaaaaaaaaaab](https://avatars.discourse-cdn.com/v4/letter/a/0ea827/32.png) [@aaaaaaaaaaaaaaaaaaab](https://forum.cursor.com/u/aaaaaaaaaaaaaaaaaaab)\
**Post date:** [December 12, 2025, 3:25pm UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/6 "2025-12-12T15:25:14Z")

</div>

Same for me, its extremely slow.

---

<div class="post-metadata">

**Author:** ![A\_T](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@A\_T](https://forum.cursor.com/u/A_T)\
**Post date:** [December 15, 2025, 5:42am UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/7 "2025-12-15T05:42:09Z")

</div>

Same for me since 2days ago

---

<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:** [January 6, 2026, 5:43am UTC](https://forum.cursor.com/t/agents-are-extremely-slow-to-respond/146032/8 "2026-01-06T05:43:08Z")

</div>

Closed on January 6, 2026, 5:43am UTC

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