Error / Message
Configuring Claude Code behind a corporate proxy
A corporate network proxy that intercepts outbound HTTPS can block Claude Code's API connection unless it's explicitly configured to route through it.
This tends to show up as connection or timeout errors that have nothing obviously to do with proxies — the first sign is usually that everything else on the network works fine except Claude Code.
Standard proxy environment variables (the same ones most CLI tools respect) are the first thing to set correctly; a proxy that also does TLS inspection may additionally need its certificate trusted by the environment Claude Code runs in.
If the organization has an internal guide for configuring CLI tools behind their specific proxy setup, that's more reliable than generic proxy troubleshooting, since corporate proxy configurations vary a lot in practice.
Set standard proxy environment variables, and trust the proxy's certificate if it does TLS inspectionFrequently asked questions
What does "Configuring Claude Code behind a corporate proxy" mean in Claude Code?
A corporate network proxy that intercepts outbound HTTPS can block Claude Code's API connection unless it's explicitly configured to route through it.
How do I fix it?
Try: Set standard proxy environment variables, and trust the proxy's certificate if it does TLS inspection
Is this something to worry about?
If the organization has an internal guide for configuring CLI tools behind their specific proxy setup, that's more reliable than generic proxy troubleshooting, since corporate proxy configurations vary a lot in practice.
Is this covered in the Claude Code Toolkit?
Yes — Configuring Claude Code behind a corporate proxy and patterns like it are part of the full command, hook, and template pack included with a Claude Code Toolkit subscription.
Want the full command, hook, and template pack?
This is one pattern out of the full Claude Code Toolkit — subscribe for the complete set, plus everything we add going forward.
Subscribe to the toolkit — $79/mo