{"version":"2.1.285","anchor":"env-var-redaction-filter-anthropic-unix-socket-aws-endpoin","canonical_anchor":"env-var-redaction-filter-anthropic-unix-socket-aws-endpoin","heading":"Some endpoint environment variables are now treated differently by Claude Code","tier":"internal","area":"Environment Variables","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/env-var-redaction-filter-anthropic-unix-socket-aws-endpoin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Some endpoint environment variables are now treated differently by Claude Code\n\nA check on environment variable names now excludes `ANTHROPIC_UNIX_SOCKET` and `AWS_ENDPOINT_URL` names, and includes `CLAUDE_CODE_API_BASE_URL` only for files\n\n**Unclear.** What this check controls, for example whether it decides which variables are passed on or hidden, is not clear.\n\n**What**\n\nClaude Code has a check that sorts environment variables by name. It now works like this:\n\n- `ANTHROPIC_UNIX_SOCKET` is always excluded.\n\n- Any variable whose name starts with `AWS_ENDPOINT_URL` is always excluded.\n\n- `CLAUDE_CODE_API_BASE_URL` is included only when the check is made for files.\n\n**Why**\n\nThese variables point Claude Code or AWS tools at a different server address. If you set any of them, how Claude Code passes them on or handles them may have changed.\n\n- Area: Environment Variables\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}