{"version":"2.1.301","anchor":"sessionconfig-path-lookup-and-global-config-locking-simplif","canonical_anchor":"sessionconfig-path-lookup-and-global-config-locking-simplif","heading":"Simplified how Claude Code locks and saves its global settings","tier":"internal","area":"Config File","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/sessionconfig-path-lookup-and-global-config-locking-simplif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Simplified how Claude Code locks and saves its global settings\n\nThe helpers that lock and save Claude Code's global settings now always use one settings file location instead of being given one\n\n**What**\n\nThe code that locks and saves Claude Code's global settings (the settings that apply across all your projects) no longer needs to be told which file to use. It always uses one location. The check for whether a project's settings are committed to the project can now also answer yes in one more case.\n\n**Why**\n\nThis is mostly internal tidying with no clear effect on what you see.\n\n- Area: Config File\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}