{"version":"2.1.277","anchor":"a-custom-header-spread-in-the-api-client-now-includes-an-ine","canonical_anchor":"a-custom-header-spread-in-the-api-client-now-includes-an-ine","heading":"A custom-header spread in the API client now includes an inert no-op spread","tier":"internal","area":"API Client","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/a-custom-header-spread-in-the-api-client-now-includes-an-ine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### A custom-header spread in the API client now includes an inert no-op spread\n\nA no-op false value was added to the API client's custom-header spread, with no apparent effect\n\n**What**\n\nWhere the client's default headers previously spread in only one extra source (the `ANTHROPIC_CUSTOM_HEADERS`-derived `anthropic-beta` values), the code now also spreads a literal `false` value immediately before it.\n\n**Why**\n\nSpreading a boolean `false` into an object has no effect, so this appears to be an inert change with no impact on the headers Claude Code sends.\n\n- Area: API Client\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}