# Debug agent fail **URL:** \ **Category:** Bug Reports\ **Tags:** debug-mode\ **Created:** [March 7, 2026, 4:32pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978 "2026-03-07T16:32:03Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![dvir\_turkenitch](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@dvir\_turkenitch](https://forum.cursor.com/u/dvir_turkenitch)\ **Post date:** [March 7, 2026, 4:32pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/1 "2026-03-07T16:32:03Z")
### Where does the bug appear (feature/product)? BugBot ### Describe the Bug 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) ### Steps to Reproduce switching to debug agent ### Expected Behavior run as expected ### Operating System MacOS ### Version Information Version: 2.5.26 VSCode Version: 1.105.1 Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0 Date: 2026-02-26T04:57:56.825Z Build Type: Stable Release Track: Default Electron: 39.4.0 Chromium: 142.0.7444.265 Node.js: 22.22.0 V8: 14.2.231.22-electron.0 OS: Darwin arm64 24.6.0 ### For AI issues: which model did you use? Auto ### 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) ### Does this stop you from using Cursor No - Cursor works, but with this issue ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [March 7, 2026, 4:46pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/3 "2026-03-07T16:46:01Z")
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](https://cursor.com/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. ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [March 8, 2026, 10:38am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/4 "2026-03-08T10:38:08Z")
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) ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [March 11, 2026, 6:06am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/6 "2026-03-11T06:06:25Z")
Connection Error for Debug still on Version 2.6.18 ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [March 13, 2026, 6:59am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/7 "2026-03-13T06:59:09Z")
@ralfzosel thanks for the update. So the update didn’t help, and the issue still reproduces on the latest versions. We’re aware of the NDJSON ingest bug in debug mode, and the team is on it. @dvir_turkenitch if you’ve updated too, please let me know whether the issue is still happening. I’ll post here once there’s progress. ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [April 3, 2026, 5:53am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/8 "2026-04-03T05:53:23Z")
I just installed Cursor 3.0.6 but the issue persists. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [April 8, 2026, 4:43pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/9 "2026-04-08T16:43:00Z")
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? ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [April 14, 2026, 7:14am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/10 "2026-04-14T07:14:00Z")
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? ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [April 20, 2026, 8:20am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/11 "2026-04-20T08:20:59Z")
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. ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [April 20, 2026, 12:18pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/12 "2026-04-20T12:18:04Z")
Thanks for your message, @deanrie . 1. Parallel sessions: It also happens if there is just _one_ Cursor window. I do not have installed VS Code (anymore) and even restarted my Mac. 2. Reload window: `Developer: Reload Window` does not help. 3. Extensions: `cursor --disable-extensions` same. 4. Port: There were some services (like `postgres` and `mysqld`) which I stopped. Now this is left: `❯ lsof -i -P | grep LISTEN` `rapportd 642 ralf 10u IPv4 0xe675a769a9388c85 0t0 TCP *:49158 (LISTEN)` `rapportd 642 ralf 11u IPv6 0x9bf223b301a3066e 0t0 TCP *:49158 (LISTEN)` `Cursor 9201 ralf 32u IPv4 0x31062ce1b63d1a9f 0t0 TCP localhost:50119 (LISTEN)` `Cursor 9207 ralf 37u IPv4 0xbd047c4c0babe8d1 0t0 TCP localhost:50084 (LISTEN)` The error persists. The Screenshot is from Cursor Version: `3.1.15` - the Request ID is: `b91a1521-4fe9-4bdd-a197-e11615943e46` ![Screenshot 2026-04-20 at 14.11.09](https://us1.discourse-cdn.com/cursor1/original/3X/d/e/dee79748a3690372b4601c995cb246444de0f08a.jpeg) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [April 26, 2026, 5:29pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/13 "2026-04-26T17:29:38Z")
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: 1. 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. 2. 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. 3. Clean user-data-dir to rule out corrupted workspace storage: 4. 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. ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [April 27, 2026, 7:32pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/14 "2026-04-27T19:32:54Z")
No. 1 did not help. There is no VPN, firewall, or proxy (No. 2). But No. 3 does help — see screenshot: ![Screenshot 2026-04-27 at 21.16.29](https://us1.discourse-cdn.com/cursor1/original/3X/9/f/9f1b0b26226f31672c105e218bd4588a15c5ee1e.png) When I start Cursor normally, the error reappears. See screenshot: ![Screenshot 2026-04-27 at 21.27.51](https://us1.discourse-cdn.com/cursor1/original/3X/5/4/540573cf158b51a5323af14af73aac91e48601c1.jpeg) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 2, 2026, 4:51pm UTC](https://forum.cursor.com/t/debug-agent-fail/153978/16 "2026-05-02T16:51:44Z")
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: 1. Fully quit Cursor. 2. Make a backup: ```auto mv ~/Library/Application\ Support/Cursor ~/Library/Application\ Support/Cursor.bak mv ~/.cursor ~/.cursor.bak ``` 3. Launch Cursor normally without `--user-data-dir`. It will create fresh folders. Sign in, switch to debug mode, send a message. It should work. 4. 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. ---
**Author:** ![ralfzosel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ralfzosel/32/100877_2.png) [@ralfzosel](https://forum.cursor.com/u/ralfzosel)\ **Post date:** [May 3, 2026, 8:58am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/17 "2026-05-03T08:58:04Z")
Thanks for your guidance — I followed steps 1–4 exactly, and the issue is now gone. Debug mode is working without errors. After restoring `~/.cursor.bak/extensions/` and restarting Cursor, a few extension-related errors appeared: - Unable to connect to Pinegrow at [http://localhost:40001/editor](http://localhost:40001/editor) - 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. Thanks again for your help! ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [May 3, 2026, 10:33am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/18 "2026-05-03T10:33:29Z")
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. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [May 25, 2026, 10:34am UTC](https://forum.cursor.com/t/debug-agent-fail/153978/19 "2026-05-25T10:34:06Z")
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.