[BUG] Desktop app does not respect NODE_EXTRA_CA_CERTS/HTTPS_PROXY (SSL interception environment)
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
In a corporate network with SSL interception (TLS inspection proxy) and a
PAC-only proxy configuration, the Claude Desktop app's Code feature fails with:
API Error: Unable to connect to API: SSL error (CERT_SIGNATURE_FAILURE)
Setting NODE_EXTRA_CA_CERTS, HTTPS_PROXY, HTTP_PROXY in ~/.claude/settings.json
("env" block) does not resolve this — the Desktop app appears to ignore these
settings.
However, the CLI (claude.exe) with the exact same certificate and proxy values
set as environment variables works correctly (claude --version succeeds).
This confirms the certificate/proxy configuration itself is correct; only the
Desktop app fails to apply it.
Also note: the /bug command itself fails with "Couldn't verify your
organization's policy for /bug. Check your network connection and try again."
in this same environment — likely hitting a policy-check endpoint that also
doesn't route through the configured proxy.
Environment: Windows, corporate network with TLS-inspecting proxy + PAC-only
proxy config (no direct outbound access).
What Should Happen?
In a corporate network with SSL interception (TLS inspection proxy) and a
PAC-only proxy configuration, the Claude Desktop app's Code feature fails with:
API Error: Unable to connect to API: SSL error (CERT_SIGNATURE_FAILURE)
Setting NODE_EXTRA_CA_CERTS, HTTPS_PROXY, HTTP_PROXY in ~/.claude/settings.json
("env" block) does not resolve this — the Desktop app appears to ignore these
settings.
However, the CLI (claude.exe) with the exact same certificate and proxy values
set as environment variables works correctly (claude --version succeeds).
This confirms the certificate/proxy configuration itself is correct; only the
Desktop app fails to apply it.
Also note: the /bug command itself fails with "Couldn't verify your
organization's policy for /bug. Check your network connection and try again."
in this same environment — likely hitting a policy-check endpoint that also
doesn't route through the configured proxy.
Environment: Windows, corporate network with TLS-inspecting proxy + PAC-only
proxy config (no direct outbound access).
Error Messages/Logs
Unable to connect to API: SSL error (CERT_SIGNATURE_FAILURE)Steps to Reproduce
In a corporate network with SSL interception (TLS inspection proxy) and a
PAC-only proxy configuration, the Claude Desktop app's Code feature fails with:
API Error: Unable to connect to API: SSL error (CERT_SIGNATURE_FAILURE)
Setting NODE_EXTRA_CA_CERTS, HTTPS_PROXY, HTTP_PROXY in ~/.claude/settings.json
("env" block) does not resolve this — the Desktop app appears to ignore these
settings.
However, the CLI (claude.exe) with the exact same certificate and proxy values
set as environment variables works correctly (claude --version succeeds).
This confirms the certificate/proxy configuration itself is correct; only the
Desktop app fails to apply it.
Also note: the /bug command itself fails with "Couldn't verify your
organization's policy for /bug. Check your network connection and try again."
in this same environment — likely hitting a policy-check endpoint that also
doesn't route through the configured proxy.
Environment: Windows, corporate network with TLS-inspecting proxy + PAC-only
proxy config (no direct outbound access).
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.259 (Claude Code)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
_No response_