{"version":"2.1.273","anchor":"remote-controlbridge-process-now-initializes-growthbook-fea","canonical_anchor":"remote-controlbridge-process-now-initializes-growthbook-fea","heading":"Remote-control\/bridge process now initializes GrowthBook feature gates at startup","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/remote-controlbridge-process-now-initializes-growthbook-fea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote-control\/bridge process now initializes GrowthBook feature gates at startup\n\nThe Remote Control bridge process now loads its feature-gate settings at startup\n\n**What**\n\nThe background process that powers Remote Control (letting Claude Code be controlled from elsewhere) now initializes its GrowthBook feature gates as part of startup, running this in parallel with the rest of its startup work. If this initialization fails, it logs an error but keeps running, falling back to a cached copy of feature gates stored on disk.\n\n**Why**\n\nThis ensures the bridge process has an up-to-date view of which features are enabled, while still working reliably (via the disk cache) if the feature-gate service can't be reached.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}