Debug agent error: Request ID: 6d15673e-3248-4426-8e89-d8b49b435425
command ‘cursor.ndjsonIngest.start’ not found
Error: command ‘cursor.ndjsonIngest.start’ not found
at GMl._tryExecuteCommand (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44162:3448)
at GMl.executeCommandImpl (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44162:2950)
at async Q_o.getConfig (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32055:7865)
at async Lpy.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44397:13439)
at async zOl.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:3793)
at async zOl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:5384)
at async zOl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837)
at async yLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752)
at async Gs (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781)
For AI issues: add Request ID with privacy disabled
Request ID: 6d15673e-3248-4426-8e89-d8b49b435425
command ‘cursor.ndjsonIngest.start’ not found
Error: command ‘cursor.ndjsonIngest.start’ not found
at GMl._tryExecuteCommand (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44162:3448)
at GMl.executeCommandImpl (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44162:2950)
at async Q_o.getConfig (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32055:7865)
at async Lpy.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44397:13439)
at async zOl.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:3793)
at async zOl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:5384)
at async zOl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837)
at async yLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752)
at async Gs (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781)
Hey, this is a known issue related to debug mode and the NDJSON ingest command.
First, you’re on version 2.5.26, which is pretty old at this point. Please update to the latest version (Help > Check for Updates, or re-download from Cursor · Download) and try debug mode again. There’s a good chance this is already fixed in newer builds.
If the issue still happens after updating, let me know. The team is aware of this, and your report helps us prioritize it.
I am on Version 2.6.13 and have the same problem, I guess:
Request ID: 654086c8-7269-492e-a316-d113d9b7b60d
command ‘cursor.ndjsonIngest.start’ not found
Error: command ‘cursor.ndjsonIngest.start’ not found
at IFu._tryExecuteCommand (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46600:3448)
at IFu.executeCommandImpl (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46600:2950)
at async Vfa.getConfig (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34183:7865)
at async nNw.execute (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46855:3389)
at async F3u.buildComposerRequestContext (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46865:3965)
at async F3u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46865:5603)
at async F3u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46865:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34308:17597)
at async Ea (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45790:4826)
Hey @ralfzosel, thanks for the update that the issue is still happening on 3.0.6.
The team is aware of this bug with debug mode and NDJSON ingest. There’s no specific ETA yet, but your reports help us prioritize. I’ll update the thread when there’s progress.
@dvir_turkenitch, are you seeing the same thing on the latest version?
I’ve updated to version 3.1.10, but debug mode still doesn’t work for me.
This is becoming quite frustrating, as I’m investing time (and tokens) into debugging without access to a feature that, from what I’ve seen on forums and Reddit, seems to work quite well for others — although I haven’t actually been able to try it myself yet. Right now, it feels like I’m paying for something I can’t actually use.
Is debug mode still working for other users on the latest versions, or are @dvir_turkenitch and I the only ones running into this? Also, is there anything I can try on my end to improve this, or any workaround available?
Hey @ralfzosel, I know this has been dragging on for a while, and it’s really frustrating to pay for a feature you can’t use.
Debug mode works for most users, so this doesn’t look like a general outage. Something specific in your environment is likely conflicting with the NDJSON ingest server. The team is tracking this exact case where the debug server does not start, but I can’t share an ETA.
To narrow it down, can you please check:
Parallel sessions: Is the same workspace open in another Cursor window, or in an old VS Code window? This is a common cause. The NDJSON port is already taken, so the command won’t register. Close all other windows and try again.
Reload window: After switching to debug mode, run Developer: Reload Window via Cmd+Shift+P, then immediately try sending a message.
Extensions: Run cursor --disable-extensions from Terminal, open the project, switch to debug mode. If it works, one of the extensions is causing it.
Port: Do you have anything else listening on local ports like Docker, another IDE, or a VPN? You can check with lsof -i -P | grep LISTEN while Cursor is running in debug mode.
If you can, please also share a full screenshot of the window at the moment the error happens. Sometimes there’s a second toast with details like port already in use or no workspace storage. Also send one fresh Request ID from version 3.1.10. That helps us tell your case apart from ones that are already fixed.
Thanks for the detailed diagnostics, it really helps narrow things down.
I noticed one important change: in the screenshot it is no longer command cursor.ndjsonIngest.start not found, it is now just Connection Error / Connection failed. So the NDJSON command is registering correctly now, but something is breaking the connection to the debug server after it starts. That is a different failure mode, so we should look at the networking side.
A few things that can help us finish this:
HTTP/2: open App Settings via Cmd+,, search for HTTP/2 and enable Disable HTTP/2, or add this to settings.json: "cursor.general.disableHttp2": true. Restart Cursor and test debug mode.
VPN, firewall, proxy: is something intercepting traffic locally? Corporate proxy, Zscaler, Little Snitch, LuLu, or similar? If yes, please temporarily disable it and try again.
Clean user-data-dir to rule out corrupted workspace storage:
Open the project, switch to debug mode, send a message. Does it work there, or does it fail the same way?
Logs from dev tools: when debug mode fails, open Help > Toggle Developer Tools, go to the Console tab, send a message, and share what shows up in the console, especially red lines and any stack traces.
We are tracking the issue. I cannot share an ETA for a fix yet, but the networking info above can help us pinpoint the cause.
Thanks a lot for testing with a clean user-data-dir, it really narrows things down.
If you look at your second screenshot from the DevTools console on a normal launch, you can see the key error: Debug server extension activation failed Error: Unknown extension anysphere.cursor-ndjson-ingest. So the bundled extension responsible for NDJSON ingest isn’t being registered in your profile, while everything works in a clean /tmp/cursor-debug-test. That means something in ~/Library/Application Support/Cursor/ (or in ~/.cursor/) is breaking registration.
To pinpoint the exact file or folder, you can try a step-by-step approach:
Launch Cursor normally without --user-data-dir. It will create fresh folders. Sign in, switch to debug mode, send a message. It should work.
If it works, you can gradually restore parts from the backup and test after each step:
First, only ~/Library/Application Support/Cursor.bak/User/settings.json and copy it into the new User/.
Then keybindings.json, snippets/.
Then ~/.cursor.bak/extensions/ (user extensions).
If the error comes back at some step, that’s your culprit.
Also, it’d help to check ~/Library/Application Support/Cursor.bak/logs/ from the last few runs, especially files like *-main.log and exthost*.log. They usually show why a bundled extension fails to load. You can search for cursor-ndjson-ingest or activation failed and share a snippet.
I know this is a bit of digging, but your current profile is the only place where this reproduces, and this will help us find what part of the state breaks extension registration. If we can narrow it down, I’ll open a tracked ticket for it.
No Beads projects found in the workspace. Initialize a project with bd init to get started.
In order to use Anysphere Remote SSH, ms-vscode-remote.remote-ssh must be uninstalled
Both Beads and Pinegrow were extensions I thought I had disabled weeks or even months ago. In fact, several other extensions were enabled that I’m quite sure I had disabled a long time ago.
Anyway, it seems likely that one of these extensions (or their state) interfered with Cursor’s debug mode. In any case, everything is working now.
Great news, thanks for running the diagnostics all the way to the end. That really helped narrow it down to the profile state.
From the extensions you listed, ms-vscode-remote.remote-ssh definitely shouldn’t be installed alongside Anysphere Remote SSH since they conflict. Pinegrow and Beads are harder to call, but they could’ve affected how bundled extensions get registered through something in the profile state.
If you’ve got time and feel like it, no pressure since everything works now, you can pinpoint the exact culprit: disable those three extensions, check debug mode, then enable them one by one and see which one makes the NDJSON ingest break again. If you find a specific extension that breaks registration of anysphere.cursor-ndjson-ingest, reply here and I’ll file a ticket with that info. It’ll help other users who might hit the same issue.
Either way, glad we got it sorted. If debug mode starts acting up again, ping this thread.
