{"version":"2.1.323","anchor":"untrusted-workspace-message-for-moved-sessions","canonical_anchor":"untrusted-workspace-message-for-moved-sessions","heading":"A clearer error when a moved session needs two trusted folders","tier":"notice","area":"Workspace Trust","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/untrusted-workspace-message-for-moved-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A clearer error when a moved session needs two trusted folders\n\nIf a session has moved but still reads settings from its starting folder, Claude Code now says both folders must be trusted\n\n**What**\n\nClaude Code asks you to trust a folder before it uses the project settings stored in it. A session (one continuous conversation) can move to a different folder while still reading its project settings from the folder it started in. In that case Claude Code now shows a specific error saying the session has moved and that both folders must be trusted. Before, it only showed the general message that the workspace had not been trusted.\n\n**Why**\n\nThis makes it clear which folders you need to trust when a moved or non-interactive session refuses to start.\n\n- Area: Workspace Trust\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}