[BUG] claude blocks on startup due to ignoring proxy settings

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?

Claude Code takes 6 minutes or longer to respond to the first prompt.

What Should Happen?

Claude should respond within seconds.

Error Messages/Logs

❯ hello                                                                                                                                                                                          

* Beaming… (16m 55s)
  ⎿  Tip: Use /btw to ask a quic

Steps to Reproduce

1. install code on a linux server behind a firewall, with network access via HTTPS_PROXY env var
2. configure in .claude/settings.json

{
  "env": {
    "CLAUDE_CODE_USE_BEDROCK": "1",
    "ANTHROPIC_DEFAULT_SONNET_MODEL": "global.anthropic.claude-sonnet-5",
    "ANTHROPIC_BEDROCK_ENDPOINT_URL": "https://redacted.bedrock-runtime.us-east-1.vpce.amazonaws.com"
  },
  "autoUpdatesChannel": "latest",
  "awsAuthRefresh": "rm -rf ~/.aws/cli/cache/* 2>/dev/null; aws sts get-caller-identity --profile ai_dev || aws sso login --profile ai_dev --no-browser"
}

1. start claude
2. enter a prompt

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.185

Claude Code Version

2.1.197

Platform

AWS Bedrock

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

An strace shows that if awsAuthRefresh is defined Claude will try to connect directly to portal.sso.us-east-1.amazonaws.com, bypassing the HTTPS proxy.
If it is not defined Claude will not try that connection and respond promptly.
The value of awsAuthRefresh does not matter, e.g. "echo dummy" will cause the same behavior".

Refreshing aws auth with the setting above worked correctly in version 2.1.185 (latest stable)

 grep connect claude.strace
connect(28, {sa_family=AF_INET, sin_port=htons(52105), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.80.2")}, 16) = 0
connect(13, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("192.168.5.10")}, 16) = 0
connect(13, {sa_family=AF_INET, sin_port=htons(3128), sin_addr=inet_addr("192.168.5.10")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect(13, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.80.2")}, 16) = 0
connect(14, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("52.204.17.243")}, 16) = 0
connect(14, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("44.196.104.60")}, 16) = 0
connect(14, {sa_family=AF_INET, sin_port=htons(0), sin_addr=inet_addr("34.195.220.130")}, 16) = 0
connect(13, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("52.204.17.243")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect(13, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("44.196.104.60")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect(13, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("34.195.220.130")}, 16) = -1 EINPROGRESS (Operation now in progress)