{"version":"2.1.305","anchor":"hybrid-settings-scope-constant-added-off","canonical_anchor":"hybrid-settings-scope-constant-added-off","heading":"New hybrid settings scope constant added","tier":"soon","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/hybrid-settings-scope-constant-added-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### New hybrid settings scope constant added\n\nA build constant `HYBRID_SETTINGS_SCOPE_REGISTERED` appears next to the plugin and project scope constants, groundwork for a new settings scope\n\n**What**\n\nA settings scope is one of the levels Claude Code reads settings from. A new build constant, `HYBRID_SETTINGS_SCOPE_REGISTERED`, was added in the same block as `PLUGINS_SCOPE_REGISTERED` and `PROJECTS_SCOPES_REGISTERED`, which are switched on (`!0`).\n\nThe two findings disagree on its value. One reports it set to true. The other quotes it as `HYBRID_SETTINGS_SCOPE_REGISTERED: !1`, which means switched off: compiled in but not active.\n\n**Why**\n\nThere is nothing for you to do yet. It suggests a hybrid settings scope is being prepared, and nothing in the findings describes how it would behave.\n\n- Area: Settings\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no\n- Present in the build but not switched on"}