{"version":"2.1.311","anchor":"hybrid-settings-scope-registered-flipped-to-true","canonical_anchor":"hybrid-settings-scope-registered-flipped-to-true","heading":"Hybrid settings scope is now registered","tier":"internal","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/hybrid-settings-scope-registered-flipped-to-true","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Hybrid settings scope is now registered\n\nA built-in switch now turns on registration of a hybrid settings scope, which was turned off in the previous build\n\n**Unclear.** It is not clear what the hybrid settings scope holds or whether it changes which settings apply to you.\n\n**What**\n\nClaude Code reads settings from several scopes, meaning separate places that each hold settings, such as those for plugins or for projects. A switch fixed into the program when it is built now registers a hybrid settings scope as well. In the previous build this switch was off. The plugin and project scopes were already registered and are unchanged.\n\n**Why**\n\nThis build registers one more place that settings can come from, alongside the ones that were already there.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}