Change:
type: 'boolean', description: localize('argv.disableLcdText', 'Disables LCD font antialiasing.') }, <ins> 'proxy-bypass-list': { type: 'string', description: localize('argv.proxyBypassList', 'Bypass any specified proxy for the given semi-colon-separated list of hosts. Example value "<local>;*.microsoft.com;*foo.com;1.2.3.4:5678", will use the proxy server for all hosts except for local addresses (localhost, 127.0.0.1 etc.), microsoft.com subdomains, hosts that contain the suffix foo.com and anything at 1.2.3.4:5678') }, </ins> 'disable-hardware-acceleration': { type: 'boolean', description: localize('argv.disableHardwareAcceleration', 'Disables hardware acceleration. ONLY change this option if you encounter graphic issues.')

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected.

Happy Coding!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore