Cursor IDE can't launch debugpy debugging configurations

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Debug launch stopped working after update. Launching (currently only Python) any configuration fails immediately with “Debug stopped” then there are 2 buttons: open launch.json or Cancel. This error happens immediately, normally launching the code takes 1-2 seconds. However, launching debugpy and attaching to the on the predefined port number works fine. I think, the IDE can’t launch the code for some reason.

Steps to Reproduce

I don’t know how to reproduce this.

Expected Behavior

Launch the code with debugpy.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.44 (user setup)
VSCode Version: 1.99.3
Commit: 9d178a4■■■89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. From your notes, it looks like Python debug launches fail right after updating to v1.7.44 on Windows, while attach still works. We haven’t seen other confirmed reports yet, so we’ll need more details to diagnose.

Could you share:

  1. Extension versions: Python and Python Debugger (debugpy)
  2. Your launch.json (please redact sensitive paths)
  3. Developer Console errors:
    Cmd/Ctrl + Shift + P → “Developer: Toggle Developer Tools” → Console tab
  4. Output panel logs: “Python” and “Debug Console” when the launch fails

Meanwhile, please try:

  • Reinstalling the Python and Python Debugger extensions
  • Cmd/Ctrl + Shift + P → “Python: Select Interpreter” to reselect your interpreter
  • Testing a minimal launch config with a simple script to see if it still fails

Let me know what you find, and we’ll proceed with escalation if needed.

Thanks! I followed your instructions, and it’s working perfectly now

1 Like

First, thanks for your interest!

Python v2025.6.1 (ms-python)
Python Debugger v2025.14.0 (ms-python)

        ...{
            "name": "Debug Dash App",
            "type": "debugpy",
            "request": "launch",
            "program": "src/apps/dash/app.py",
            "console": "integratedTerminal",
            "cwd": "${workspaceFolder}",
            "justMyCode": false,
            "stopOnEntry": false,
            "python": "${command:python.interpreterPath}",
            "env": {
                "PYTHONPATH": "${workspaceFolder}"
            }
        },...

Actually, these might be relevant before attempting to debug:

ERR [/c:/Users/user/.cursor/extensions/ms-python.vscode-python-envs-1.2.0-win32-x64]: Extension is not compatible with Code 1.99.3. Extension requires: ^1.100.0-20250407.
error @ workbench.desktop.main.js:55
workbench.desktop.main.js:55 ERR [/c:/Users/user/.cursor/extensions/ms-python.vscode-python-envs-1.6.0-win32-x64]: Extension is not compatible with Code 1.99.3. Extension requires: ^1.104.0-20250815.
error @ workbench.desktop.main.js:55

Perhaps also relevant:

ERR An unknown error occurred. Please consult the log for more details.
Object
code
:
“ENOENT”
errno
:
-4058
path
:
“C:\Program Files\Git\usr\bin\bash.exe”
spawnargs
:
(6) [‘-O’, ‘extglob’, ‘-c’, ‘snap=$(command cat <&3) && builtin shopt -s extglo…p_bash_state >&4; builtin exit $COMMAND_EXIT_CODE’, ‘–’, ‘echo test’]
syscall
:
“spawn C:\Program Files\Git\usr\bin\bash.exe”
[[Prototype]]
:
Object

  • Reinstalling those two extensions did not help.
  • Selecting the global interpreter instead of the venv one did also not help.
  • I think that my config is minimal. But here is my test:
{
            "name": "Debug Hello World",
            "type": "debugpy",
            "request": "launch",
            "program": "hello_world.py",
            "console": "integratedTerminal",
            "cwd": "${workspaceFolder}",
            "justMyCode": false,
            "stopOnEntry": false,
            "python": "${command:python.interpreterPath}",
            "env": {
                "PYTHONPATH": "${workspaceFolder}"
            }
        }
#!/usr/bin/env python3
"""
Simple hello world script for testing debugging in Cursor IDE
"""

def main():
    print("Hello, World!")
    
    # Set a breakpoint here for testing
    name = "Cursor IDE"
    print(f"Hello from {name}!")
    
    # Another breakpoint target
    numbers = [1, 2, 3, 4, 5]
    total = sum(numbers)
    print(f"Sum of numbers: {total}")

if __name__ == "__main__":
    main()

Actually, it seems that the new Python debugger (2025.14.0) is the culprit. Reverting back to 2025.10.0 solved my problem.

1 Like

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