{"version":"2.1.227","anchor":"settings-loading-caches-ownership-and-the-real-home-director","canonical_anchor":"settings-loading-caches-ownership-and-the-real-home-director","heading":"Settings loading caches ownership and the real home directory","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/settings-loading-caches-ownership-and-the-real-home-director","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Settings loading caches ownership and the real home directory\n\nSettings loading caches file ownership checks, so startup does less repeated work.\n\n**What**\n\nSettings loading now caches file ownership for the project root, its `.git` entry and its `.claude` entry, plus a resolved home directory, and reports read problems as structured issues instead of raw errors.\n\n**Details**\n\n- A home directory that cannot be resolved raises \"home directory realpath unavailable\"; a file that cannot be read produces a fatal issue reading \"Settings file could not be read: ...\".\n- The managed-settings locations (\/Library\/Application Support\/ClaudeCode, C:\\Program Files\\ClaudeCode, \/etc\/claude-code) and the drop-in directory beside them moved into a resettable holder.\n- The settings directory is now created before every write, not only when the file was missing.\n\n**Evidence**\n\n`home directory realpath unavailable`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}