{"version":"2.1.245","anchor":"an-unused-internal-setting-slot-named-autofixprmode","canonical_anchor":"an-unused-internal-setting-slot-named-autofixprmode","heading":"An unused internal setting slot named autofixPrMode","tier":"soon","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.245\/e\/an-unused-internal-setting-slot-named-autofixprmode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.245","markdown":"### An unused internal setting slot named autofixPrMode\n\nA settings key named autofixPrMode is listed but undefined, so setting it does nothing.\n\n**What**\n\nThe settings registry lists an internal key `autofixPrMode` but never defines or reads it, so it cannot be set to anything and changes nothing. It is the likely future switch for choosing how `\/autofix-pr` runs.\n\n**Details**\n\n- The name appears exactly once, at the end of the display order for the Internal settings group, alongside `snipEnabled`, `doneMeansMerged` and `autoUploadSessions`.\n- No setting definition backs it, nothing writes it, and no code consults it when picking the autofix path.\n- It was already present in 2.1.243 in the same inert state.\n\n**Evidence**\n\n`\"autofixPrMode\"`\n\n- Area: Slash Commands\n- Names: `autofixPrMode`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}