{"version":"2.1.246","anchor":"remote-managed-settings-can-defer-their-consent-prompt-to-th","canonical_anchor":"remote-managed-settings-can-defer-their-consent-prompt-to-th","heading":"Remote managed settings can defer their consent prompt to the next interactive session","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/remote-managed-settings-can-defer-their-consent-prompt-to-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Remote managed settings can defer their consent prompt to the next interactive session\n\nIf managed settings need consent and nothing can prompt you, it's deferred to your next interactive session.\n\n**What**\n\nWhen remote managed settings need your consent but the current command cannot display a prompt, Claude Code now logs that the prompt is deferred to the next interactive session rather than reporting only that no consent surface exists. Either way it keeps running on the settings you last consented to, and the fetch is marked unsuccessful.\n\n**Details**\n\n- The older message, `No consent surface in this interactive session`, is still the fallback.\n- Which of the two paths runs is decided by a runtime check in the command itself, not by any settings key.\n\n**Evidence**\n\n`Remote settings: Consent prompt deferred to the next interactive session (this command cannot host it); keeping the consented baseline`\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}