{"version":"2.1.305","anchor":"feature-flag-host-gains-a-profile-hook","canonical_anchor":"feature-flag-host-gains-a-profile-hook","heading":"Feature-flag clients gain a profileFlagHost hook","tier":"internal","area":"Internals","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/feature-flag-host-gains-a-profile-hook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Feature-flag clients gain a `profileFlagHost` hook\n\nFeature-flag client setups gain a `profileFlagHost` hook, and a Google sign-in token exchange client gets its own transporter\n\n**What**\n\nFeature flags are switches Claude Code reads to turn behaviour on or off. This release adds a hook to the code that sets them up, plus an unrelated small change in Google sign-in.\n\n- `profileFlagHost`: the feature-flag client setup now includes a `profileFlagHost` hook, and a served-bearer SDK client configuration gains a version of it that does nothing.\n\n- Google token exchange: the Google sign-in client that exchanges credentials (STS) now gets its own `Gaxios` transporter, the component that sends its web requests, built from the existing transporter's default settings.\n\n**Why**\n\nNeither change alters anything you see. The hook looks like internal plumbing. The transporter change may mean the token exchange now follows the same default settings, such as proxy settings, as other Google sign-in requests.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}