Agent timeout within 16 seconds, chat no longer working

[master3395]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When trying to write anything into the cursor in v2.5.0, it fails to execute.
I have then tried to downgrade to 2.3.35, it works fine, except the browser doesn’t have the tools 2.5 has, to allow ip usage.

The agent execution provider did not respond within 16 seconds. This may indicate the extension host is not running or is unresponsive.

Steps to Reproduce

I simply upgraded the cursor from 2.4, and it failed.

Expected Behavior

It would continue to fill out the request

Operating System

Windows 10/11

Version Information

Version: 2.5.0-pre.56.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: d416bdcd7387e58abd3dde9a4cc484c6ca4f9ad0
Date: 2026-02-09T08:43:02.892Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto.

For AI issues: add Request ID with privacy disabled

Request ID: c920b40d-90e5-43e8-a887-a6bb720132c0
{“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/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:42676:7143
at async Thv.createExecInstance (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:42676:5189)
at async J7b (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:536:555601)
at async NH.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:31462:6603)
at async u1l.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:42643:1196)
at async Fty.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43734:14052)
at async PLl.buildComposerRequestContext (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43745:3810)
at async PLl.streamFromAgentBackend (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43745:5401)
at async PLl.getAgentStreamResponse (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43745:9960)
at async KPe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:31506:15588)
at async Object.Mo [as onSubmit] (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:42739:4779)
at async vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:42713:65338

Additional Information

Cursor seems to become more and more unstable, for each version that comes, i do know i sometimes use the “Nightly” versions to test the new versions, but even stable versions have issues, such as 2.4 that is really unstable, i had to go back to 2.3, which now lacks browser options.

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, this is a known issue where the extension host process crashes and causes a 16-second timeout. It’s been reported in a few versions, including 2.4.x and now 2.5.0.

A few things to try:

1. Clear the workspace database (this helps a lot of users):

   • Fully close Cursor
   • Delete or rename this file: C:\Users\[your username]\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
   • Restart Cursor (you’ll need to sign in again)

2. Start without extensions to rule out an extension conflict:

   • Run in a terminal: cursor --disable-extensions
   • If it works, enable extensions one by one to find the one causing it

3. Full reinstall. Sometimes a clean install fixes leftover state issues after updates

The team is aware and actively tracking this.

Also, here’s a related thread with more context: Agent-execution-time-out

Let me know if any of the steps helped.