Just updated and having this issue:
2.4.14
f46acd1f4f453807331ae59ea4c94fabd2b40640
x64
I just updated cursor and iâm now facing this issue
iâve tried the disable mode but nothing works
Version: 2.4.14 (Universal)
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
1 Like
Looks to be resolved under
Version: 2.4.19 (user setup)
VSCode Version: 1.105.1
Commit: 33d874341d80e1ffcb3fd3e5f2bb854d2b69a570
Date: 2026-01-22T07:02:12.951Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045
Version: 2.4.20 (user setup)
VSCode Version: 1.105.1
Commit: 20b56586b0785b8843487045393c57c6d89b7100
Date: 2026-01-22T07:38:04.757Z
Build Type: Stable
Release Track: Nightly
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631
Looks to have resolved:
Version: 2.4.21
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Nightly
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Still having this problem in
Version: 2.4.23 (user setup)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
The problem still exists!
Version: 2.4.9
VSCode Version: 1.105.1
Commit: 4119c25a8bbcda34554ee91403218e9964bfa880
Date: 2026-01-21T04:10:36.693Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Linux x64 6.14.0-37-generic
Request ID: 28414f28-9066-4bc5-bfbb-09cf061dd1c3
{âerrorâ:âERROR_CUSTOMâ,âdetailsâ:{âtitleâ:âAgent Execution Timed Outâ,âdetailâ:âThe agent execution provider did not respond within 16 seconds. This may indicate the extension host is not running or is unresponsive.â,âisRetryableâ:false,âshouldShowImmediateErrorâ:true,âadditionalInfoâ:{},âbuttonsâ:[{âlabelâ:âReload Windowâ,âreloadWindowâ:{}}],âplanChoicesâ:}}
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11430:8256
at async Qqf.createExecInstance (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11430:6308)
at async sNg (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async vW.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9094:16084)
at async Nka.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11430:1205)
at async yab.execute (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34238:14275)
at async vpc.buildComposerRequestContext (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:3573)
at async vpc.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:5171)
at async vpc.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34248:8436)
at async LTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9168:76988)
at async Object.Hi [as onSubmit] (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:33000:3808)
at async vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32974:59943
1 Like
Same here:
Version: 2.4.31 (system setup)
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200
Edit:
The strange thing is that it seems to happen in some Code workspaces /project folders and doensât happen in other codespaces/project folders.
(Even when they are in the same language, just different apps for the same platform etc)
1 Like
Iâm getting the same problem with the newest version I have access to - Version: 2.5.17 - if I install 2.4 it goes away.
I think I figured out the problem - I had a corrupted git object in the workspace. I ran into this error repeatedly in just one workspace - It didnât occur in other projects. Disabling extensions (including via extension bisect), clearing workspace storage, and restarting the extension host had no effect.
The key clue was that renaming the .git folder immediately stopped the crashes. Then I ran git fsck which showed multiple bad sha1 file errors inside .git/objects.
The fix was simply to reclone the repository from the remote. After replacing the corrupted local copy with a fresh clone, git fsck returned clean results and the extension host crashes stopped completely.