Hi! Sent some messages in the PR thread but better news is I think we already have a solution that may work for you! There is a option to configure serverReadyAction which is built-in and works for all debug configs. This is the doc about it: https://code.visualstudio.com/Docs/editor/debugging#_automatically-open-a-uri-when-debugging-a-server-program. I gave it a try on my side and it seemed to do the correct thing so let me know if it works for you! Thanks

Hmm yeah that is a valid alternative to work with. So basically this sets the serverReadyAction manually, whereas the proposed autoStartBrowserURL would do this automatically

looping in @connor4312 since he is the expert of this setting, wondering if he has any advice to make it automatic or better for your use case

Yea. I don't know how the Python implementation of autoStartBrowserURL works, but serverReadyAction might work for you. It's quite manual and explicit but it should be reliable.

maybe serverReadyAction should support AI power in the future to figure out the URL from program output magically, but we aren't there right now :)

The python implementation you mean from debugpy or from the debugger extension? I looked and the debugger passes on the arguments without editing

looping in @rchiodo as well

AFAIK, debugpy doesn't handle the autoStartBrowser configuration. The extension does here:

Not sure if that means the serverReadyAction wouldn't work because there would be duplicates?

Yea, looks like that would overwrite serverReadyAction if present

Hi! I have put in a fix for this so it doesn't overwrite the setting if present, @maxschmi if you are able to get the most recent pre-release version of the vscode python debugger (latest released should say this morning) and give it a try to let me know if that works that would be great, thanks!

Hey @eleanorjboyd

I'm not so sure what to test. I did install the latest pre-release, but the "autoStartBrowserURL" option is not available. But I guess you decided against the pattern option.

If I have :

"name": "Django server",
"type": "debugpy",
"request": "launch",
"program": "${workspaceFolder:python}\\manage.py",
"args": [
	"runserver",
	"localhost:8000"
],
"django": true,
"autoStartBrowser": true,
"serverReadyAction": {
	"pattern": "Starting development server at http://localhost:([0-9]+)/",
	"action": "openExternally",
	"uriFormat": "http://localhost:%s"
}

The "serverReadyAction" is executed, but unfortunatly is not detecting or not using the correct port, but instead uses 3000 as a port.
As far as I see, the "autoStartBrowser" option is more less ignored. Is that the excpected outcome?