Cursor AI Agent can not complete task

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I asked AI agent to complete the task, but it constantly fails

Steps to Reproduce

Install cursor
create new chat
ask question

Expected Behavior

No error should happen.

Operating System

Linux

Version Information

Version: 2.7.0-pre.45.patch.0
VSCode Version: 1.105.1
Commit: 447839e5318c8d58f2447eeeca8f440ae1b72d09
Date: 2026-03-10T05:34:36.213Z
Build Type: Nightly
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: add Request ID with privacy disabled

Request ID: d7734393-6836-4d7f-8fcd-a0431e122116
[internal] The debug configuration was not set up properly
rhe: [internal] The debug configuration was not set up properly
    at MXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:24192)
    at LXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:23095)
    at GXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:6285)
    at jVd.run (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:10557)
    at async XK.runAgentLoop (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47390:11392)
    at async yLh.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:9454)
    at async yLh.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:14941)
    at async BGe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34884:17909)

Request ID: 4d947bab-86cc-44ac-b8a7-8f928e86afdb
[internal] The debug configuration was not set up properly
rhe: [internal] The debug configuration was not set up properly
    at MXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:24192)
    at LXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:23095)
    at GXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:6285)
    at jVd.run (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:10557)
    at async XK.runAgentLoop (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47390:11392)
    at async yLh.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:9454)
    at async yLh.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:14941)
    at async BGe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34884:17909)

Request ID: bb10654d-4041-4db6-86fb-3bc59c3f10c0
[internal] The debug configuration was not set up properly
rhe: [internal] The debug configuration was not set up properly
    at MXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:24192)
    at LXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34802:23095)
    at GXw (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:6285)
    at jVd.run (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34803:10557)
    at async XK.runAgentLoop (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47390:11392)
    at async yLh.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:9454)
    at async yLh.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47443:14941)
    at async BGe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor%20Nightly.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34884:17909)

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report with the stack traces and request IDs.

This error pattern (“The debug configuration was not set up properly” in the agent loop) looks like a Nightly-only regression. A couple of similar agent loop crashes have been reported recently on Stable builds too, but with different error messages. So the Nightly build might have an extra issue.

A few things to try:

  1. Switch to Stable: Since you’re on Nightly (2.7.0-pre.45), try the Stable release (2.6.18) and see if the issue still happens. This will help confirm if it’s a Nightly regression.

  2. Start a completely fresh chat: Create a new chat from scratch and don’t continue an existing conversation. Some agent loop errors happen because the conversation state is corrupted.

  3. Pick a specific model instead of Auto (if you’re using Auto): Try Claude Sonnet or another model directly.

Let me know if switching to Stable fixes it, or if you see the same error there too.

4

yes, I resolved it by starting new chat.

This chat was the first one after the fresh installation. I suppose this belongs to some initialization.

Also This chat was started not like inside project and/or workspace. What I did I opened the folder with project and store the current window as workspace. After that I see ‘local’ appeared and the problem gone.

Probably, because tehre were no project, chat agent was confused from which directory to start.

I hope this helps to make Cursor better.

6

Glad you figured it out. That really is the root cause. The agent needs an open workspace or folder to work properly.

The error message “The debug configuration was not set up properly” isn’t very clear in this case. I’ll share this feedback with the team so that if there’s no workspace open, you’ll see a more helpful message instead of that stack trace.

1 Like
7

Is there a way to track is this proposition accepted or when this feature will be implemented?

10

At the moment, we don’t have a public tracker for individual feature requests. But I’ve already shared your feedback about improving this error message with the team, and it’s been noted.

1 Like