Cursor latest "nightly" fails to run both plan and agent

[master3395]

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Chat errors, idk why, it seems to time out.
I had to downgrade to 2.6.12, then it worked.
I was testing out 2.7.0

Version: 2.6.12 (user setup)
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
Release Track: Nightly
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Steps to Reproduce

When i tried asking the cursor to update a few files, it timed out, almost instantly.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Now i have Version: 2.7.0-pre.27.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: f8f2f830ec68bfe59992d7a8c5cf84b863809dc0
Date: 2026-03-06T05:45:01.293Z
Build Type: Stable
Release Track: Nightly
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
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: 93ce8a06-54de-4078-bfc4-0e88cee2034c
{“error”:“ERROR_CUSTOM”,“details”:{“title”:“Agent Execution Timed Out”,“detail”:“The agent execution provider did not respond in time. 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:43782:12719
at async $Hy.createExecInstance (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43782:10479)
at async kxA (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34042:582497)
at async xJ.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34243:6603)
at async $Bu.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43782:1323)
at async iNw.execute (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46855:2775)
at async N3u.buildComposerRequestContext (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:3965)
at async N3u.streamFromAgentBackend (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:5603)
at async N3u.getAgentStreamResponse (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46865:13663)
at async fMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34308:17597)
at async Object.ka [as onSubmit] (vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45790:4828)
at async vscode-file://vscode-app/d:/Users/USER/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45764:56755

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, I see you’ve hit this again. It’s the same “Agent Execution Timed Out” error as last time, but now on nightly 2.7.0.

Since you’re on the nightly track, regressions like this can happen between builds. Here are a few things to try on 2.7.0:

• Clear the workspace state again. Old state from 2.6.x can conflict with 2.7.0:

  • Fully close Cursor
  • Delete or rename: C:\Users\[your username]\AppData\Roaming\Cursor\User\globalStorage\state.vscdb
  • Reopen Cursor. You’ll need to sign in again

• Start without extensions: cursor --disable-extensions

  • If it works, turn them back on one by one to find which one is causing it

• If neither helps, staying on 2.6.12 is a solid workaround until the next nightly build ships with a fix.

Let me know how it goes.