[BUG] settings.json Proxy Configuration Doesn't Work for Claude (But CLI Does)

[CallisteH]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

My app needs to have no proxy to work.
If I do this in ~/.claude/settings.json

{
  "env": {
    "ANTHROPIC_BASE_URL": "<base-url>",
    "ANTHROPIC_AUTH_TOKEN": "<token>",
    "CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS": "1",
    "CLAUDE_CODE_TELEMETRY_DISABLED": "1",
    "https_proxy": "",
    "HTTP_PROXY": "",
    "http_proxy": "",
    "HTTPS_PROXY": ""
  },
  "model": "haiku"
}

Claude blocks. It takes the proxy that is in my bashrc.

Now, if I do this:

HTTPS_PROXY="" HTTP_PROXY="" https_proxy="" http_proxy="" claude

Claude works.
I should note that I tried NO_PROXY="*", and it doesn't work.

What Should Happen?

Claude should be able to reach my base URL without a proxy, just like it does when we pass proxy arguments with the command.

Error Messages/Logs

❯ bonjour
⎿  API Error: Connection error. (after several minutes)

Steps to Reproduce

Steps to Reproduce

Prerequisites:

• A proxy is configured in your system bashrc (e.g., export https_proxy=...)
• Your API URL works without the proxy (e.g., curl --proxy "" https://<base-url> succeeds)

Test 1 - settings.json (FAILS):

{
  "env": {
    "ANTHROPIC_BASE_URL": "<base-url>",
    "https_proxy": "",
    "HTTP_PROXY": "",
    "http_proxy": "",
    "HTTPS_PROXY": ""
  }
}

Result: Claude blocks

Test 2 - CLI (WORKS):

HTTPS_PROXY="" HTTP_PROXY="" https_proxy="" http_proxy="" claude

Result: Claude connects successfully

Expected: Both methods should work the same way.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.25

Platform

Other

Operating System

Other Linux

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

❯ /doctor
Diagnostics └ Currently running: native (2.1.25)
└ Path: /home//.local/share/claude/versions/2.1.25
└ Invoked: /home//.local/share/claude/versions/2.1.25
└ Config install method: native
└ Search: OK (bundled)

Updates
└ Auto-updates: enabled
└ Auto-update channel: latest
└ Stable version: 2.1.7
└ Latest version: 2.1.25

Version Locks
└ 2.1.25: PID 180758 (running)

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] HTTPS_PROXY is not applied to the Anthropic API POST requests when set in ~/.claude/settings.json #11660
2. [BUG] Native binary installation ignores HTTP_PROXY for API streaming requests (Bun fetch issue ?) #14165
3. [BUG] Claude Code intermittently ignores HTTP_PROXY on startup (Windows) #15212

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[CallisteH]

Ok I installed claude from the binary. Maybe the is the problem.. I'm ready to close exept if someone confirms the bug with others installs ?

I will try with npm later and if yes, it's a duplicate of #14165

[bhilton]

Confirming I am seeing this as well. Regardless of how it is provided (bash env or settings.json env) versions newer than 2.1.22 do not honor NO_PROXY.

[CallisteH]

Confirming I am seeing this as well. Regardless of how it is provided (bash env or settings.json env) versions newer than 2.1.22 do not honor NO_PROXY.

Do you have Claude's installation via the binary? Or npm ?

[bhilton]

Confirming I am seeing this as well. Regardless of how it is provided (bash env or settings.json env) versions newer than 2.1.22 do not honor NO_PROXY.

Do you have Claude's installation via the binary? Or npm ?

This is the binary install. It is affecting everyone on our team.

[bhilton]

Confirming I am seeing this as well. Regardless of how it is provided (bash env or settings.json env) versions newer than 2.1.22 do not honor NO_PROXY.

Do you have Claude's installation via the binary? Or npm ?

This is the binary install. It is affecting everyone on our team.

The issue is still present with the recently released 2.1.29, FYI.

[CallisteH]

ok thanks for your reply @bhilton
So for now the workaround is to run claude with env vars in the command directly

HTTPS_PROXY="" HTTP_PROXY="" https_proxy="" http_proxy="" NO_PROXY="*" claude

[bhilton]

ok thanks for your reply @bhilton So for now the workaround is to run claude with env vars in the command directly

HTTPS_PROXY="" HTTP_PROXY="" https_proxy="" http_proxy="" NO_PROXY="*" claude

Sorry, I think this Issue may be discussing two different problems.

1. settings.json may not support disabling proxy settings such as HTTP_PROXY by setting them to the empty string (not an issue that is affecting me, but may be real)
2. NO_PROXY does not work anymore regardless of how I supply it (env var, settings.json, direct from the cli as you typed - which is actually just setting an env var anyway). Our team has had to remain on 2.1.22 in order to use NO_PROXY.

[saidelike]

Duplicate of #22752