{"version":"2.1.314","anchor":"new-managed-settings-key-responsecomparisonenabled","canonical_anchor":"new-responsecomparisonenabled-setting","heading":"New responseComparisonEnabled setting turns off two-answer comparisons","tier":"use","area":"Managed Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/new-managed-settings-key-responsecomparisonenabled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### New responseComparisonEnabled setting turns off two-answer comparisons\n\nA new responseComparisonEnabled setting lets you stop Claude Code showing two answers to one message and asking which is better\n\n**Unclear.** What `responseComparisonEnabled` does and what its default value is are not known.\n\n**What**\n\nA new setting, `responseComparisonEnabled`, controls whether Claude Code may show you two answers to one message and ask which is better. Its description reads: \"Set to false to stop Claude Code from showing two answers to one message and asking which is better.\" When the setting is absent or true, Claude Code may do this on some turns.\n\nThe setting is also recognised by the code that merges managed settings (settings an organisation administrator can set for everyone), in the same list as `autoContinueAtUsageLimit` and `remoteControlAtStartup`. It is described as an internal setting.\n\n**Why**\n\nIf you are occasionally shown two answers and asked to pick one, setting `responseComparisonEnabled` to `false` stops those prompts, and administrators can set it through managed settings.\n\n- Area: Managed Settings\n- Names: `responseComparisonEnabled`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}