{"version":"2.1.301","anchor":"config-home-null-handling-memory-rules-and-skills-paths-sk","canonical_anchor":"config-home-null-handling-memory-rules-and-skills-paths-sk","heading":"Claude Code can run without a user settings folder","tier":"notice","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/config-home-null-handling-memory-rules-and-skills-paths-sk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude Code can run without a user settings folder\n\nWhen there is no user settings folder, Claude Code now skips your personal CLAUDE.md, rules, skills and memory instead of looking for them\n\n**Unclear.** It is not clear what makes Claude Code run without a user settings folder.\n\n**What**\n\nClaude Code normally keeps your personal settings in a folder in your home directory. These include your own `CLAUDE.md`, rules, skills and memory. Claude Code can now run without that folder. When there is none, it skips those files: loading skills from it returns nothing, and lookups that would use it are passed over.\n\nIn the same situation, a check also changes how two things work: passing through permission to write files, and remapping paths inside a worktree, a separate working copy of a project.\n\n**Why**\n\nThis points to a way of running Claude Code with no personal settings folder at all. Normal use is likely unchanged.\n\n- Area: Diskless Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}