Very long executions for agent commands

[bintocher]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

very long executions for agent commands

Steps to Reproduce

• open clean project folder
• use in agent chat mode - agent+auto
• write message : “check git status”

Expected Behavior

command (git status) execution took 40-46 seconds!

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.6 (Universal)
VSCode Version: 1.99.3
Commit: 9455eaa4c87f2bad91eda3f2bc9b42b16eae1080
Date: 2025-09-11T01:16:54.096Z (10 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Auto, but i test also - gpt5, sonnet4, gemini25, grok4-code-fast-1, etc…

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report, we’ll look into it.

[Naeem_Rehmat]

I have been experiencing the same issue for the last three days.

[andrewh (Andrew Milich)]

Hey! This one was fixed in 1.6.11, with an update coming soon with more fixes.

[bintocher]

not fixed in 1.6.11 @andrewh

look at video

Version: 1.6.11 (Universal)

VSCode Version: 1.99.3

Commit: ea659ac512725d8ba835e9e77b826949d829d680

Date: 2025-09-11T15:12:12.526Z (3 hrs ago)

Electron: 34.5.8

Chromium: 132.0.6834.210

Node.js: 20.19.1

V8: 13.2.152.41-electron.0

OS: Darwin arm64 24.6.0

[bintocher]

just now update cursor ide, bug is here too

Version: 1.6.14 (Universal)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:42:07.958Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

[andrewh (Andrew Milich)]

Could you try restarting Cursor and reporting back to us?

[bintocher]

Of course, I restarted the cursor, I even rebooted my mac mini.
If you had written down where the debug logs are, I would have sent them long ago.
Due to the fact that this is a critical cursor ide problem, I made a decision and rolled back to version 1.5 - there are no such problems there.

[bintocher]

omg, i use stable version in settings, and cursor just update to 1.6.23, bug is still here, how to work???

what logs i can send to dev-team for fix this bug ?

[bintocher]

has the bug been fixed or not? I’m working on an older version of cursor, the error is not reproducible here.

Version: 1.5.11
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

[bintocher]

bug still here:

Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

1. cursor was updated automatically - why??
2. what debugging information should be provided to finally resolve this issue?
3. or write how to completely reinstall the cursor

my macos version

[bintocher]

bug fixed in new version YAY!

Version: 1.7.28
VSCode Version: 1.99.3
Commit: adb0f9e3e4f184bba7f3fa6dbfd72ad0ebb8cfd0
Date: 2025-10-01T02:45:21.769Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0