{"version":"2.1.277","anchor":"api-client-builder-gains-a-permissioncontext-parameter-and-q","canonical_anchor":"api-client-builder-gains-a-permissioncontext-parameter-and-q","heading":"API client builder gains a permissionContext parameter and querySource default","tier":"internal","area":"API Client","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/api-client-builder-gains-a-permissioncontext-parameter-and-q","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### API client builder gains a permissionContext parameter and querySource default\n\nThe internal API client builder gained a permissionContext parameter and a querySource setting\n\n**Unclear.** What permissionContext and querySource actually affect in the client's behavior is not described in this finding.\n\n**What**\n\nThe internal function that builds the Anthropic API client, handling headers, authentication, and provider routing for Bedrock, Vertex, Foundry, gateway, and similar setups, now accepts a new `querySource` parameter, which defaults to the existing `source` value, and a new `permissionContext` parameter. Some existing fields were also renamed to `agentContext`, `credentials`, and `storageV5`.\n\n**Why**\n\nThis finding shows the API client builder gaining new inputs but does not describe what they change in the client's behavior.\n\n- Area: API Client\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}