{"version":"2.1.323","anchor":"working-directory-changes-keep-project-settings-from-the-lau","canonical_anchor":"working-directory-changes-keep-project-settings-from-the-lau","heading":"Changing folders mid-session keeps project settings from the launch folder","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/working-directory-changes-keep-project-settings-from-the-lau","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Changing folders mid-session keeps project settings from the launch folder\n\nWhen the project folder is pinned, changing directory tells Claude that settings, MCP servers and skills still come from where the session started\n\n**Unclear.** It is not stated which apps pin the project folder.\n\n**What**\n\nSome apps that start Claude Code can pin the project folder, which is the folder project settings are read from. When it is pinned and the working directory changes during a session, Claude Code now tells the model that these still come from the folder where the session was launched:\n\n- project settings\n\n- MCP servers (add-ons that provide extra tools)\n\n- skills\n\nPermission rules written in the new folder count only if both folders are trusted. Before, Claude Code always said settings now came from the new folder.\n\n**Why**\n\nThis matters for apps such as the desktop app that pin the project folder, because the model now has an accurate picture of where its settings come from.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}