"Investigate Error In Chat" key binding not working

“Investigate Error in Chat” with Ctrl-Shift-D was working yesterday when I first started using Cursor. Shortly after starting, it stopped working. Key bindings showed a conflict with: “View: Debug and Run”. I changed the key binding for that to Ctrl-Shift-Alt-D so as not to conflict with “Investigate Error in Chat”, but it doesn’t seem to work still.

When I hit Ctrl-Shift-D, the popup dialogue box does disappear, but it doesn’t transfer anything to chat, so I’m unsure where the disconnect in the feature is. Perhaps the Ctrl-Shift-D IS triggering the action, but maybe it just fails to hand off the prompt to chat? Just spitballing here.

Editing to add: Other functions similar to this do not work, such as Ctrl-Shift-L. It opens a new chat, but does not transfer any highlighted code to the new chat.

Edit 2: It fails to function with the attached screenshot, “Missing function or method docstring” from pylint. It DOES work with other errors such as a “requests” method missing a timeout argument.

Cursor version info below. Windows 11, 64-bit.

Version: 0.50.5 (user setup)
VSCode Version: 1.96.2
Commit: 96e5b01ca25f8fbd4c4c10bc69b15f6228c80770
Date: 2025-05-18T04:26:31.444Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22621

:white_check_mark: Check the forum to ensure the issue hasn’t been reported already
I don’t see any reports of the issue.
:lady_beetle: Provide a clear description of the bug
Hopefully done.
:counterclockwise_arrows_button: Explain how to reproduce the bug (if known)
Unknown.
:camera: Attach screenshots or recordings (e.g., .jpg, .png, .mp4).
Done, but no idea how helpful that will be in this case.
:laptop: Tell us your operating system and your Cursor version (e.g., Windows, 0.x.x).
Provided above.
:prohibited: Tell us if the issue stops you from using Cursor.
It does not stop me from using it, but it does take away one of the most useful features of the editor.

Hey, it works for me. Maybe something is intercepting this shortcut, like an extension or an installed program.

OK, so it only KINDA fails for me.

In the screenshot above, I’m asking it to investigate the message about no docstring existing. That fails to work, but it DOES work with other errors like missing timeouts for requests.

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