Create a launch configuration

Create a launch configuration to debug app.py. Add an entry named DebugApp that starts the Python interpreter with the current file, passes argument --mode=dev, sets workingDirectory to the project root, and stops on entry. Save the configuration in launch.json so it appears in the Run and Debug panel and can be started with F5.

Before I add this launch.json entry for the team's repo, make it easy to approve: put the program, args, and cwd at the top so non-developers can see them, call out any environment variables injected into the config, and flag anything that will break when another dev uses a different Python interpreter. Recommend two small edits to make the config review-ready.

I added DebugApp to launch.json for app.py with stopOnEntry true and args --mode=dev, but pressing F5 attaches to another Python process and I get breakpoints that never hit. I think the workspace has a background test runner or my debug port is conflicting. I cannot tell whether my configuration needs a unique port, an attach instead of launch, or a change in console settings. What is the most likely fix and how do I implement it quickly for my Linux workstation?

Developers keep making bespoke launch.json entries for local debugging, which leads to inconsistent breakpoints and confusion about env vars. I want a single practice that reduces this repetition and makes debug configs easy to adopt across projects. Which habit should I change first so launch configurations are reliable and shareable for the whole team?