{"version":"2.1.288","anchor":"launch-folder-key-handling-added-to-settings-and-a-settings","canonical_anchor":"launch-folder-key-handling-added-to-settings-and-a-settings","heading":"Groundwork for limiting which settings a launch folder can supply","tier":"soon","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/launch-folder-key-handling-added-to-settings-and-a-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Groundwork for limiting which settings a launch folder can supply\n\nClaude Code's settings code gained handling for which settings keys come from the folder it was launched in, with no visible effect yet\n\n**Unclear.** Which settings keys are involved, and whether the empty panel field is ever shown, were not traced.\n\n**What**\n\nClaude Code's settings code gained a way to decide how settings keys coming from the folder you launched it in are treated. By default they are taken as read, as before. The settings panel gained a matching field that is always empty for now.\n\n**Why**\n\nNothing changes in practice yet. It looks like preparation for controlling which settings a project folder is allowed to set.\n\n- Area: Settings\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no\n- Present in the build but not switched on"}