{"version":"2.1.227","anchor":"auth-token-and-custom-header-failures-now-say-which-value-is","canonical_anchor":"auth-token-and-custom-header-failures-now-say-which-value-is","heading":"Auth token and custom header failures now say which value is wrong","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/auth-token-and-custom-header-failures-now-say-which-value-is","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Auth token and custom header failures now say which value is wrong\n\nBad auth tokens and custom headers now each get a message naming the exact value to fix.\n\n**What**\n\nThree specific one-line messages replace a single generic one, so a bad value points at its own source: \"Invalid auth token \u00b7 Fix external auth token\", \"Invalid ANTHROPIC_CUSTOM_HEADERS \u00b7 Fix the environment variable\", and \"Invalid request header from the environment \u00b7 Fix the environment variable\".\n\n**Details**\n\n- Which message you get depends on whether the offending value came from `ANTHROPIC_CUSTOM_HEADERS` or from another header source.\n\n**Evidence**\n\n`Invalid ANTHROPIC_CUSTOM_HEADERS \u00b7 Fix the environment variable`\n\n- Area: Auth\n- Names: `ANTHROPIC_CUSTOM_HEADERS`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}