[{"data":1,"prerenderedAt":22},["ShallowReactive",2],{"doc:en:settings-network":3},{"title":4,"lede":5,"html":6,"headings":7},"Settings: Network","The “Network” tab of the settings configures the HTTP(S) proxy and TLS certificate checking for Claude Code, quotas, integrations, and updates.","\u003Ch2 id=\"open-the-tab\">Open the tab\u003C\u002Fh2>\n\u003Cp>Open the settings with \u003Ccode class=\"key\">Ctrl+,\u003C\u002Fcode> (\u003Ccode class=\"key\">⌘,\u003C\u002Fcode> on macOS), then choose “Network” (“HTTP(S) proxy and TLS certificates for Claude Code, integrations, and updates”). These are the app’s settings, shared by all projects; they apply on “Save”.\u003C\u002Fp>\n\u003Cp>They matter behind a company network: a proxy to get out, and sometimes a certificate the proxy imposes. Without a proxy, there’s nothing to set here.\u003C\u002Fp>\n\u003Ch2 id=\"proxy\">Proxy\u003C\u002Fh2>\n\u003Cp>The app says so under the group’s title: “Claude Code processes, quota reads, integrations, and updates all go through the proxy. It applies to agents the next time their process (re)starts.”\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>Effect\u003C\u002Fth>\n\u003Cth>Default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“HTTP(S) proxy”\u003C\u002Ftd>\n\u003Ctd>The proxy’s address, for example \u003Ccode>http:\u002F\u002Fuser:password@proxy:3128\u003C\u002Fcode>. Empty (“none”), connections are direct.\u003C\u002Ftd>\n\u003Ctd>Empty\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Exclusions”\u003C\u002Ftd>\n\u003Ctd>The hosts that don’t go through the proxy, separated by commas (the \u003Ccode class=\"key\">NO_PROXY\u003C\u002Fcode> list).\u003C\u002Ftd>\n\u003Ctd>\u003Ccode class=\"key\">localhost,127.0.0.1\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>“Also apply the proxy to the built-in terminals”\u003C\u002Ftd>\n\u003Ctd>Terminals also get the proxy variables.\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"what-goes-through-the-proxy\">What goes through the proxy\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Claude Code processes\u003C\u002Fstrong>: agents, and the other calls to Claude Code that Escouade makes (naming an agent, commit messages, signing in to an account). They get \u003Ccode class=\"key\">HTTPS_PROXY\u003C\u002Fcode>, \u003Ccode class=\"key\">HTTP_PROXY\u003C\u002Fcode>, their lowercase variants, and \u003Ccode class=\"key\">NO_PROXY\u003C\u002Fcode> (with \u003Ccode class=\"key\">no_proxy\u003C\u002Fcode>) if “Exclusions” isn’t empty. An agent only sees them the next time its process (re)starts: an agent already running keeps its settings until then.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quota reads and integrations\u003C\u002Fstrong> (Jira, Trello, GitHub Issues, Linear): the app’s requests go through the proxy and respect “Exclusions”.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Updates\u003C\u002Fstrong>: checking and downloading go through the proxy. An invalid proxy address makes the check fail, with the message “invalid proxy address”.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Built-in terminals\u003C\u002Fstrong>: only if “Also apply the proxy to the built-in terminals” is on. The same variables are then added to terminals, launch commands, and worktree commands. See \u003Ca href=\"\u002Fen\u002Fdocs\u002Fterminals\u002F\">terminals\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Without a proxy address, Escouade adds no proxy variable: processes keep your session’s environment.\u003C\u002Fp>\n\u003Ch2 id=\"certificates\">Certificates\u003C\u002Fh2>\n\u003Cp>The app says so under the group’s title: “Integrations, quotas, and updates trust recognized certificates and those installed on this system (usually a corporate proxy’s). Claude Code has its own list.”\u003C\u002Fp>\n\u003Cdiv class=\"table\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>Effect\u003C\u002Fth>\n\u003Cth>Default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>“Skip TLS certificate verification”\u003C\u002Ftd>\n\u003Ctd>Escouade no longer verifies TLS certificates. For a proxy that decrypts traffic with an unrecognized certificate (the “UnknownIssuer” error).\u003C\u002Ftd>\n\u003Ctd>Off\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>When on, the setting applies to integrations, quotas, and updates, and to Claude Code processes (the next time their process starts): they get \u003Ccode>NODE_TLS_REJECT_UNAUTHORIZED=0\u003C\u002Fcode>, which the commands agents run (npm, node…) inherit too. It doesn’t apply to the built-in terminals or to launch commands.\u003C\u002Fp>\n\u003Cdiv class=\"callout warning\">\u003Cp class=\"callout-title\">Warning\u003C\u002Fp>\u003Cp>Use it only on a network you trust: an intercepted connection, tokens included, would no longer be detected. If your proxy has its own certificate, install it on the system rather than turning verification off: integrations, quotas, and updates will recognize it (Claude Code has its own list).\u003C\u002Fp>\n\u003C\u002Fdiv>\n",[8,12,15,19],{"id":9,"text":10,"depth":11},"open-the-tab","Open the tab",2,{"id":13,"text":14,"depth":11},"proxy","Proxy",{"id":16,"text":17,"depth":18},"what-goes-through-the-proxy","What goes through the proxy",3,{"id":20,"text":21,"depth":11},"certificates","Certificates",1791926756674]