{"version":"2.1.321","anchor":"feature-flag-client-hastens-the-first-payload","canonical_anchor":"feature-flag-client-hastens-the-first-payload","heading":"Remote Control tool host gets its feature settings sooner after startup","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/feature-flag-client-hastens-the-first-payload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control tool host gets its feature settings sooner after startup\n\nClaude Code's feature-settings client can refresh faster at startup until the first fresh values arrive, and Remote Control's tool host uses this\n\n**What**\n\nClaude Code fetches feature settings from Anthropic's servers to decide which features are on. Before, it always waited the full refresh interval before its first refresh. It can now start refreshing at once and use shorter waits until fresh settings arrive. The waits grow each time and are varied by up to 10% at random.\n\nRemote Control can run as a tool host, a background process that offers local tools to cloud sessions. That host uses this faster start, and it gains diagnostics recording when its first settings arrive and what requests it handles.\n\n**Why**\n\nSessions controlled through Remote Control get the right feature settings sooner after they start.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}