Cursor Agents from "Agent Window" don't work after v3.1.17 update

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since updating to v3.1.17 from 3.1.15 this morning, I can’t run any agent from the Agents Window. Every time I run an agent I am given

“The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: 543b20a7-5dbc-4b12-a90e-d799a7371b06”

This persists depite restarting the application numerous times. Keep in mind agent execution from editor mode works fine (don’t know about from agent mode because that view seems to have been removed…). I also ran a network diagnostics and everything passed with 0 issues.

Steps to Reproduce

  1. Open the “agents window”

  2. try and run a new agent in agent mode with any prompt

  3. Wait for pop up error

Expected Behavior

The agent should be able to interpret the prompt and provide output.

Screenshots / Screen Recordings

Screenshot 2026-04-20 115117.png
Screenshot 2026-04-20 115117.png372×153 4.06 KB

Operating System

Windows 10/11

Version Information

Version: 3.1.17 (user setup)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Claude Opus 4.7

For AI issues: add Request ID with privacy disabled

Request ID: 543b20a7-5dbc-4b12-a90e-d799a7371b06

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey thanks for the report. This looks like a known issue. In the Agents Window layout Glass, the workspace trust prompt does not show up, so cursor-agent-exec never activates. That is why editor mode works but Agents Window does not. We are tracking the issue.

Try this workaround:

  • Close Cursor.
  • Open your project folder in classic mode. In a terminal run cursor --classic <path to project> or open Cursor, switch the layout to classic or editor, then open the folder.
  • You should see the dialog Do you trust the authors of the files in this folder. Click Yes, I trust the authors.
  • Switch back to the Agents Window layout.

After that, the agent should start normally. Let me know if it worked.

If it did not help, it might be a second Windows bug with cursor-socket. Open PowerShell as admin and share the output of:

dir "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"

If you see dist\ but not out\, tell me and I will share a symlink fix.

8

I’m having this same issue on macOS, on multiple repos that were working fine last Friday, in both Agent and Editor (classic) views.
I already tried launching via the `cursor --classic`, fully restarted Cursor, tried opening other workspaces, etc., and still can’t get it to work. Are there any other alternatives or other logging I could provide for this?

9

After running that command as admin, it seems to be the case where dist\ is present but not out\

image
image875×127 3.3 KB

10

@andrew0517 OK, that confirms the second bug with cursor-socket. The out/ folder is missing, and only dist/ exists. This is a known packaging regression that has now also affected the Windows build.

Workaround: create a symlink out -> dist. Close Cursor, open PowerShell as Administrator, and run:

cd "$env:LOCALAPPDATA\Programs\cursor\resources\app\extensions\cursor-socket"
New-Item -ItemType SymbolicLink -Path "out" -Target "dist"

If PowerShell complains about permissions, you can do the same thing in Admin cmd:

cd /d "%LOCALAPPDATA%\Programs\cursor\resources\app\extensions\cursor-socket"
mklink /D out dist

After that, start Cursor and try the agent in the Agents Window again.

Important: after the next Cursor update, the symlink might get removed, so you may need to repeat this. The bug is being tracked and a permanent fix is in progress, but I can’t share an ETA.

@ovasquez On macOS, this might be the same cursor-socket bug. Check the folder contents:

ls "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket/"

If you see dist but no out, apply the same workaround on macOS:

cd "/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-socket"
ln -s dist out

Then restart Cursor. If the out folder already exists, or the output is different, share what you see, plus your Cursor version from About, and the Request ID from the failure.

11

@deanrie to confirm that your suggestion fixed this issue. And in case it helps anything:

Version: 3.1.17
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
Layout: editor
Build Type: Stable
Release Track: Default
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