Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
I received this bug:
[09b07dda-4d0b-45fc-823d-4a6d5868b0d8] socks forwarding established
2026-02-03 12:03:41.533 [info] [command][3513e0d0-b0d5-4cfb-b636-c880b48ee899] Process exited with code 0
2026-02-03 12:03:41.533 [info] [forwarding][multiplex][127.0.0.1:56236 → 127.0.0.1:56227 → 127.0.0.1:44195][09b07dda-4d0b-45fc-823d-4a6d5868b0d8] socks connection closed
2026-02-03 12:03:41.534 [info] [command][3513e0d0-b0d5-4cfb-b636-c880b48ee899] Socket close event received
This happened after the recent update!
Steps to Reproduce
NA
Operating System
MacOS
Version Information
Version: 2.4.27
VSCode Version: 1.105.1
Commit: 4f2b772756b8f609e1354b3063de282ccbe7a690
Date: 2026-01-31T21:24:58.143Z (2 days ago)
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 24.4.0
For AI issues: add Request ID with privacy disabled
Request ID: 6df8290d-cdb1-4429-b50d-03d0dca9ca8d
{“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”:}}
Agent Execution Timed Out [deadline_exceeded]
ConnectError: [deadline_exceeded] Agent Execution Timed Out
at vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:8256
at async sWf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async dMg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:549852)
at async _W.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async l1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async Pcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34235:14275)
at async jpc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:3573)
at async jpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:5171)
at async jpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14623)
at async Object.Ei [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32968:59730
Does this stop you from using Cursor
Yes - Cursor is unusable