{"version":"2.1.311","anchor":"proxy-auth-helper-pinned-to-the-proxy-it-was-started-for","canonical_anchor":"proxy-auth-helper-pinned-to-the-proxy-it-was-started-for","heading":"Organization proxy sign-in helper only sends credentials to its own proxy","tier":"notice","area":"Network Proxy","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/proxy-auth-helper-pinned-to-the-proxy-it-was-started-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Organization proxy sign-in helper only sends credentials to its own proxy\n\nIf `proxyAuthHelper` is set by your organization and the proxy in use is not the one it started for, Claude Code sends no credential\n\n**What**\n\nThe `proxyAuthHelper` setting runs a helper that supplies a credential for a network proxy. When the helper comes from your organization and the proxy now in use is not the one it was started for, Claude Code no longer sends the credential and warns: \"proxyAuthHelper is the organization's and the proxy in use is not the one it was started for: no credential sent\". Before, the helper ran every time.\n\n**Why**\n\nThis keeps an organization's proxy credential from being sent to a different proxy.\n\n- Area: Network Proxy\n- Names: `proxyAuthHelper`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}