Composer-2 not connecting

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Composer 2 not working/connecting

Steps to Reproduce

Use composer 2 as far as i can tell

Expected Behavior

composer 2 cant connect

Operating System

MacOS

Version Information

Version: 2.7.0-pre.140.patch.0
VSCode Version: 1.105.1
Commit: ccfa72ce1f439af527c44b009c67fb94169b1100
Date: 2026-03-26T01:58:51.913Z
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

Composer-2

For AI issues: add Request ID with privacy disabled

Request ID: 79659a27-a55f-44b2-9edc-e160ad607606
{“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”:}}
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive.
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:46222:15925
at async PQw.createExecInstance (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46222:13037)
at async TEy (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:36639:616603)
at async zF.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:36847:4462)
at async zdd.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46222:1749)
at async iL_.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49230:2772)
at async t_d.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49240:3976)
at async t_d.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49240:5859)
at async t_d.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49240:16220)
at async f4e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:36952:20418)

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey, this is a known issue. The extension host can stop responding, and requests to the agent can time out before they reach the server. The team is aware and is tracking it.

A few things to try:

  1. Switch to Stable. You’re on Nightly 2.7.0-pre.140.patch.0, and the extra instability can make this worse. Cursor Settings > Release Track > Default.

  2. Close all chat tabs and start a new chat. Sometimes older sessions grow memory usage and can freeze the IDE.

  3. Delete the workspace state DB. Fully quit Cursor, then delete it, back it up first:
    ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb
    Then restart.

  4. Try without extensions. Run cursor --disable-extensions from Terminal to check if something is conflicting.

  5. Disable HTTP/2. Settings > search cursor.general.disableHttp2 > true > restart.

If none of that helps, try a clean reinstall. Remove ~/Library/Application Support/Cursor before reinstalling.

Let me know how it goes.

8

Hey @Panos_Zepos!

The ‘Waiting for Extension Host’ / agent execution timeout issue has been addressed in a recent Cursor update. Updating to the latest version should resolve this.