{"version":"2.1.287","anchor":"remote-tools-readiness-now-waits-for-the-first-flag-fetch","canonical_anchor":"remote-tools-readiness-now-waits-for-the-first-flag-fetch","heading":"Remote tools wait for feature settings to load before handling calls","tier":"internal","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-tools-readiness-now-waits-for-the-first-flag-fetch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote tools wait for feature settings to load before handling calls\n\nBefore judging remote tool calls, Claude Code now also waits a limited time for its first download of feature settings\n\n**Unclear.** How long the time limit for the flag download is was not stated.\n\n**What**\n\nFeature flags are switches that can turn behaviour on or off without a new release. When Claude Code starts serving tools to a remote caller, it gets ready before it decides whether to allow any calls. Getting ready used to mean waiting for these:\n\n- plugin hooks\n\n- remote managed settings\n\n- policy limits\n\nIt now also waits for its first download of feature flags, up to a time limit. The debug log records whether that download landed or was not heard in time.\n\n**Why**\n\nSwitches that affect remote tools are now read from their real values when calls are judged. Claude Code no longer relies on built-in fallbacks just because the download had not finished yet.\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}