Agent-execution-time-out

chase_butterfly · January 22, 2026, 3:50am

Describe the Bug

Request ID: 434d6bd6-8e09-4af0-9d02-4d75b972a60d
{“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 WHf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async YNg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async wW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async r1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async gcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34229:14275)
at async Wpc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:3573)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:5171)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Object.Oi [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32965:59943

Steps to Reproduce

Request ID: 434d6bd6-8e09-4af0-9d02-4d75b972a60d
{“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 WHf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async YNg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async wW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async r1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async gcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34229:14275)
at async Wpc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:3573)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:5171)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Object.Oi [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32965:59943

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.4.14
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
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

For AI issues: add Request ID with privacy disabled

Request ID: 434d6bd6-8e09-4af0-9d02-4d75b972a60d
{“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 WHf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async YNg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async wW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async r1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async gcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34229:14275)
at async Wpc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:3573)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:5171)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Object.Oi [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32965:59943

Does this stop you from using Cursor

Yes - Cursor is unusable

hojunin-29cm · January 22, 2026, 3:58am

exactly same as me.

same version. after update to current version, every single request are disabled

Version: 2.4.14
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

mhbl · January 22, 2026, 3:59am

I’m experiencing the exact same issue.
Hardware context:
Version: 2.4.14
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

chillenious · January 22, 2026, 4:08am

Same problem, entirely unable to use Cursor, right after upgrading.

Version: 2.4.14

VSCode Version: 1.105.1

Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640

Date: 2026-01-22T02:35:05.148Z (1 hr 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 25.2.0

ak_rs · January 22, 2026, 4:08am

Same here. Updated 10 mins ago.

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 x64 25.2.0

sir · January 22, 2026, 4:08am

I encountered the same issue.

dylean · January 22, 2026, 4:09am

Same. How to solve this problem.

Aleksandr_Rivankov · January 22, 2026, 4:09am

bad update(

chrisbrine · January 22, 2026, 4:10am

Same issue

BiscuitCoder · January 22, 2026, 4:11am

version 2.4.14

After the update, all extensions and basic functions seem to be disabled, making it impossible for me to use the cursor. Please fix this quickly; this is a very irresponsible update, and I will consider unsubscribing.

Aman_Jain1 · January 22, 2026, 4:11am

Same issue

klaRRk · January 22, 2026, 4:11am

I uninstalled Cursor and install with old installer that I have. Now I’m on version 2.3.37 and it’s working. New update is broken.

Dave_Grice · January 22, 2026, 4:12am

Same. Just updated to v2.4.14. Git is installed and all is working well in VSCode.

Version: 2.4.14 (user setup)
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: Windows_NT x64 10.0.26200

VILKA · January 22, 2026, 4:13am

Same issue, don’t update to new version. Its broken

Request ID: ff5c5bc9-f5fa-4c37-ab3e-d03b98bfc4a8
{“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 WHf.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:6308)
at async YNg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:529:549377)
at async wW.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:16084)
at async r1a.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11431:1205)
at async gcb.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34229:14275)
at async Wpc.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:3573)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:5171)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Object.Oi [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32991:3808)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32965:59943

deanrie · January 22, 2026, 4:14am

Hey everyone, I see that version 2.4.14 is broken. The extension host is crashing with an error “No Connect transport provider registered”, which is causing Agent and everything else to stop working. I’ve already reported this to the team.

Temporary fix - downgrade to 2.3.37:

@klaRRk has already confirmed that the downgrade works. Here’s what you need to do:

Uninstall your current version of Cursor
Download the old version 2.3.37 from Download · Cursor. You’ll find the “Previous versions” section at the bottom of the page

BiscuitCoder · January 22, 2026, 4:15am

i hope curosr team can be more reponsible for each verion update, i‘m fed up this irreponsible and random bad update

ZulfikarHD · January 22, 2026, 4:17am

i’m on windows and have the same issue, all extension is disabled or crashed

Vu_Le_Anh1 · January 22, 2026, 4:17am

Same issue

aheck1969 · January 22, 2026, 4:19am

Same issue here, updated minutes ago to v2.4.14

Version: 2.4.14
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

BiscuitCoder · January 22, 2026, 4:19am

This is not the correct solution. Please fix it as soon as possible.

Topic		Replies	Views
Extension host terminated Help extensions , crashes	27	632	February 12, 2026
After last update, stuck at "Waiting for extension host" Bug Reports installation , extensions , crashes	20	3002	February 16, 2026
The agent execution provider did not respond within 4 seconds. This may indicate the extension host is not running or is unresponsive Bug Reports extensions , performance	13	2157	January 31, 2026
Cursor stops working - Connection Error Bug Reports java	119	4586	January 12, 2026
Stuck with timeouts? Help java	48	2633	February 4, 2026

Agent-execution-time-out

Describe the Bug

Steps to Reproduce

Operating System

Current Cursor Version (Menu → About Cursor → Copy)

For AI issues: add Request ID with privacy disabled

Does this stop you from using Cursor

Related topics