{"version":"2.1.280","anchor":"sdk-apply-flag-settings-and-sdk-update-settings-switched-to","canonical_anchor":"sdk-apply-flag-settings-and-sdk-update-settings-switched-to","heading":"sdk_apply_flag_settings and sdk_update_settings switched to a different wrapping helper","tier":"internal","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/sdk-apply-flag-settings-and-sdk-update-settings-switched-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### sdk_apply_flag_settings and sdk_update_settings switched to a different wrapping helper\n\nSDK methods applyFlagSettings and updateSettings now route through a different internal wrapper function\n\n**Unclear.** The finding does not say what behavior, if any, differs as a result of using the new wrapper function.\n\n**What**\n\nTwo methods used by the Claude Code SDK's query client, `applyFlagSettings` and `updateSettings`, now send their asynchronous requests through a different internal helper function than before. The SDK is the toolkit that lets code outside Claude Code drive it programmatically, and `updateSettings` is the method that lets that outside code change settings.\n\n**Why**\n\nThis is an internal plumbing change: the finding does not indicate any difference in what `applyFlagSettings` or `updateSettings` do or how they're called, only that a different underlying function now carries the request.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}