{"version":"2.1.281","anchor":"remote-control-and-other-policy-gated-features-latched-an","canonical_anchor":"remote-control-and-other-policy-gated-features-latched-an","heading":"Remote Control and other policy-gated features: 'latched' and 'cache_miss' messages now come before the no-taint fallback","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-and-other-policy-gated-features-latched-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control and other policy-gated features: 'latched' and 'cache_miss' messages now come before the no-taint fallback\n\nA policy-gated feature that is latched off now always shows \"Restart Claude Code to re-evaluate.\" instead of a generic fallback\n\n**What**\n\nSome features, such as Remote Control, can be turned off by an organization's policy. Claude Code has helpers that explain why such a feature is unavailable. Before, they returned a generic fallback message early whenever no policy restrictions were recorded.\n\nThat early exit is gone. Two cases are now checked first:\n\n- Latched: the feature was switched off and stays off until Claude Code restarts. This now shows \"Restart Claude Code to re-evaluate.\" even when no policy restrictions are recorded.\n\n- Cache miss: the policy answer was not available.\n\nThe fallback text is now used only when the organization denied the feature or no answer came back.\n\n**Why**\n\nWhen Remote Control or a similar feature is unavailable because it was switched off earlier in the run, the message now says to restart instead of giving an unrelated generic reason."}