Incorrect debugpy command selected in terminal

Before creating a new issue, please check the FAQ to see if your question is answered there.

Notes

We have debugpy python package installed locally and running debugpy in the VSCode terminal selects the local installation instead of the bundled extension wrapper in .vscode-server/extensions/ms-python.debugpy-2025.18.0/bundled/scripts/noConfigScripts/debugpy. This broke since debugpy 1.8.5, which added the debugpy script to the python package. This happens because the extension wrapper path is added to the end of PATH rather than beginning. Can the extension be modified to prepend the bundled path to the front of PATH instead?

Environment data

• debugpy version: 1.8.16 (run import debugpy; print(debugpy.__version__) if uncertain)
• OS and version: Red Hat Enterprise Linux 8.10 (Ootpa)
• Python version (& distribution if applicable, e.g. Anaconda): 3.11.13
• Using VS Code or Visual Studio: Yes

Actual behavior

In VSCode terminal when we run debugpy <python-filename>. Instead of attaching a debugger, it gives us the help menu.

Expected behavior

Running debugpy <filename> should select the debugy version bundled with the ms-python.debugpy extension and attach the debugger.

Steps to reproduce:

1. Install Debugpy version 1.8.16 on the system using pip.
2. Open the project in VSCode
3. Download the Python Debugger Extension (@id:ms-python.debugpy) V2025.18.0
4. Try debugging a python file by running debugpy <filename> in VSCode Terminal.

Start by tracing the extension code that adds the bundled path .vscode-server/extensions/ms-python.debugpy-2025.18.0/bundled/scripts/noConfigScripts/debugpy to the VS Code terminal PATH. Reproduce the issue with debugpy 1.8.16 and verify that prepending this path makes debugpy <filename> attach the debugger rather than show the help menu.