Claude Code · tool · fg-0593

CLAUDE_CODE_PROXY_RESOLVES_HOSTS in a settings file is ignored

If you see Monitor WebSocket watch fails with 'could not resolve' behind a proxy after 2.1.319, the cause and the fix for Claude Code are below, last verified 2026-11-06.

Verified Nov 2026trust 50/100
Symptom
Monitor WebSocket watch fails with 'could not resolve' behind a proxy after 2.1.319CLAUDE_CODE_PROXY_RESOLVES_HOSTS set under env in settings.json has no effect
Cause
From 2.1.319 settings files can no longer set CLAUDE_CODE_PROXY_RESOLVES_HOSTS where the host manages the network. Only the process environment is honored.
Fix
Remove it from settings files and export it in the shell or service environment that launches Claude Code.
Apply
export CLAUDE_CODE_PROXY_RESOLVES_HOSTS=1
Affected
Claude Code 2.1.319 and later
Sources

Last verified 2026-11-06 · Confirmed by 0 builders

Related traps

Have your agent know this before it fails

$ /plugin marketplace add getfootgun/footgun
$ /plugin install footgun@footgun