Currently we can match Chrome's stdout if we aren't using pipe debugging to get the uri to attach to. It would be helpful to also be able to do this on arbitrary/Node targets. We have something like this in the "serverReadyAction" (which is a separate, built-in extension in vscode). It allows launching and triggering debugWithChrome that launches a browser. An attachWithChrome could be a convenient addition to that, with the standard output that Chrome writes being the default pattern. https://code.visualstudio.com/updates/v1_32#_automatically-open-a-uri-when-debugging-a-server-program

I think it should still be opt-in switch rather than automatic; if some random 3rd party was able to print to the console somehow (e.g. if a server logged request bodies), we wouldn't want that to cause the user's machine to connect to some arbitrary server.

Probably will not get to this issue this iteration/month, likely next month.

/cc @pavelfeldman