VS Code holds onto parent console when launched via command line

Repro:

1. Open cmd.exe
2. Run code
3. Switch back to cmd.exe
4. exit

Repro’s in stable and insiderrs and does not repro in Atom which is also on Electron 2.

Advice from Windows console team:

I believe VSCode is reconnecting to its parent hosting console for debugging purposes.

Starting with @joaomoreno who might know who to send this to, not sure who the real owner is though.

[dweddig01]

Any updates on this. Reading through the comments is a little confusing if this is planned to be fixed, or not. What is weird, is it use to work where running “code .” from the command line did NOT seem to hijack the PowerShell 7 session. But now it does it again. I do have a newly installed computer so there may be a behavior related to some kind of setting?

[jtnord]

Any update on this? It’s a minor but extremely annoying issue.

not really minor as your shell (cmd.exe) becomes almost useless as it has debug logs spewed to it which makes reading what you should have there almost impossible.

Note: there are people saying “use code.bat” not “code.exe” however - that workaround does not work when you use start some_file_with_type_registered_to_code. for example if you associate xml files with code via the windows explorer (always open with) and then from a cmd.exe shell run start test.xml which is pretty basic windows behaviour you get the debug messages in the console. You can not change the association to code.bat as that spawns a new console window when you open the file from explorer

Edit: sorry, just now noticed the linked PR; really appreciate you all working on it!

the upstream PR has been closed and so appears stalled for real this time.