devtools opening source files in a new instance of VSCODE when "open source files in VSCODE" is on

Hello.

I am running VSCODE and Microsoft Edge (in the 'experiments' focus mode for devtools) and since then CSS files are no-longer editable inside devtools as they might be when you click on a CSS file that is applying a rule to an element.  I had a look at the devtools "Settings" for the experiments tab and  and there is a checkbox to turn on/off 'Open Source Files in VSCODE'.  Which explains why the file was not editable in devtools.

This seems like a good feature, except it is opening a new instance of VSCODE when I click on a CSS file to edit it, and that seems odd as I already have an instance of VSCODE open, and am indeed running the project from the VSCODE live server.

Is it intentional that with this setting selected it should open the files in VSCODE in a new process?  It feels a bit messy that it is not in the instance that I am running the project from, but in a new one and I may already have that CSS file open in the original instance and would prefer to edit it there.

If I am doing this wrong, and maybe should be running devtools in VSCODE (which I understand is new) then I'll try that, but I found this quite confusing today and it was only luck that I found the tickbox that turned on/off "Open source files in Visual Studio Code".

thanks in advance.