proxy

To set shell environment variables for HTTP proxy routing, source the proxy.sh script to apply configuration modes like laptop, covisist, or unset to the current session. This adjusts HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY for safe, targeted routing without hard-coding application settings.

The best way to avoid hard-coding proxy configurations is to manage proxy environment variables for the current shell session. This approach provides guidance for tools like curl, git, and npm to respect the shell-level proxy settings rather than requiring individual application configurations.

Yes, you can use different proxy modes like laptop and covisint in the same shell session. The skill implements management of proxy variables by allowing you to source proxy.sh to switch between local and global proxy configurations or unset them entirely.

Yes, the proxy skill manages both uppercase and lowercase environment variables. It explicitly implements management of HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY alongside their lowercase variants to ensure broad compatibility across typical development tools.

You need to source the script to apply proxy settings because environment variables must be exported into the current shell process. Running a script directly executes it in a subshell, meaning the HTTP_PROXY and NO_PROXY configurations would be lost when the subshell exits.