Debug mode not working

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Debug mode is not working, I have pro plan and I have tokens included, the rest of cursor works

Steps to Reproduce

I open the debug mode and it doesn’t not provide any answer, I have tried reinstalling cursor, chache, sign in again and again, and nothing works

Expected Behavior

Debug shoudl provide answers and work

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z (3 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report.

This is a known issue with the “Proceed” button in Debug mode. The team is already tracking this bug.

Workaround: instead of clicking “Proceed”, manually enter this prompt in chat:
Issue reproduced. Please proceed.

This should let Debug mode continue the analysis.

Could you also share the Request ID from Debug mode (top-right chat menu > Copy Request ID)? That’ll help us add your case to the issue tracking.

Let me know if the workaround helped.

3

image
image712×1612 49.9 KB
it doesn’t work, I don’t have ID because it doesn’t show messages.

4

FWIW, I just used it earlier today and had no issue. Also used Grok Code. I’m not sure I used any buttons through. I think I just switched to debug, told it where to setup the logging and then chatted with it. Sorry if this is unhelpful.

Version: 2.2.44 (Universal)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
1 Like
5

Thanks for the info.

Try the following:

  1. Open the developer console (Help > Toggle Developer Tools)
  2. Go to the Console tab
  3. Click “Proceed” again
  4. Copy any red errors that appear

Also check:

  • Does the issue reproduce in a new project/folder?
  • Does the regular Agent mode (not Debug) work?

This will help the team diagnose the problem better.

6

these are the errors i have [composer] Error in AI response Error: command ‘cursor.ndjsonIngest.start’ not found
at Wdo._tryExecuteCommand (workbench.desktop.main.js:13008:3342)
at Wdo.executeCommandImpl (workbench.desktop.main.js:13008:2847)
at async eas.getConfig (workbench.desktop.main.js:614:11326)
at async KK.getNewMessageContext (workbench.desktop.main.js:10005:706)
at async KK.submitChatMaybeAbortCurrent (workbench.desktop.main.js:9988:12231)
at async bo (workbench.desktop.main.js:12254:3831)

and the second one

composer] Failed to get complete AI response
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:9994
await in submitChatMaybeAbortCurrent
(anonymous) @ workbench.desktop.main.js:52
ehr @ workbench.desktop.main.js:52
hFd @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
bo @ workbench.desktop.main.js:12254
await in bo
onSubmit @ workbench.desktop.main.js:12254
le @ workbench.desktop.main.js:12030
onSubmit @ workbench.desktop.main.js:12030
handleSubmit @ workbench.desktop.main.js:12024
(anonymous) @ workbench.desktop.main.js:12026
Igl @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444
Rgl @ workbench.desktop.main.js:444
BQ @ workbench.desktop.main.js:444
update @ workbench.desktop.main.js:446
Igl @ workbench.desktop.main.js:444
bu @ workbench.desktop.main.js:444
D7d @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444
workbench.desktop.main.js:13074 [composer] Chat incomplete or aborted {arch: ‘arm64’, platform: ‘darwin’, channel: ‘stable’, client_version: ‘2.2.44’, requestId: ‘abc206db-e4c5-40fd-9d40-de1b219d4c63’, …}
_log @ workbench.desktop.main.js:13074
warn @ workbench.desktop.main.js:13074
submitChatMaybeAbortCurrent @ workbench.desktop.main.js:9994
await in submitChatMaybeAbortCurrent
(anonymous) @ workbench.desktop.main.js:52
ehr @ workbench.desktop.main.js:52
hFd @ workbench.desktop.main.js:52
n.value @ workbench.desktop.main.js:52
bo @ workbench.desktop.main.js:12254
await in bo
onSubmit @ workbench.desktop.main.js:12254
le @ workbench.desktop.main.js:12030
onSubmit @ workbench.desktop.main.js:12030
handleSubmit @ workbench.desktop.main.js:12024
(anonymous) @ workbench.desktop.main.js:12026
Igl @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444
Rgl @ workbench.desktop.main.js:444
BQ @ workbench.desktop.main.js:444
update @ workbench.desktop.main.js:446
Igl @ workbench.desktop.main.js:444
bu @ workbench.desktop.main.js:444
D7d @ workbench.desktop.main.js:444
(anonymous) @ workbench.desktop.main.js:444

7

Thanks for the logs, they really help.

The cursor.ndjsonIngest.start not found error is a known issue, and the team is already working on a fix.

1 Like
8

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.