{"version":"2.1.295","anchor":"cloud-session-restore-notice-adjusted-when-foreign-files-are","canonical_anchor":"cloud-session-restore-notice-adjusted-when-foreign-files-are","heading":"Cloud session restore can keep files Claude Code did not create","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-session-restore-notice-adjusted-when-foreign-files-are","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Cloud session restore can keep files Claude Code did not create\n\nWith keepsForeignFiles, cloud restore cleanup leaves foreign files in place and warns that deny and ask rules may not be in force\n\n**Unclear.** When this wording is shown instead of the other restart notices is not known.\n\n**What**\n\nWhen a cloud session's environment is restarted, Claude Code restores your settings into it. Files there that Claude Code did not create are called foreign files.\n\n- When `keepsForeignFiles` is set, the cleanup step now leaves a foreign path in place and reports `kept_foreign` instead of removing it.\n\n- `keepsForeignFiles` depends on a `foreignFiles` setting not being `replaced`.\n\n- The restore result now also records `keepsForeignFiles` and `sidecarCountedAsAbsent`.\n\n- With `keepsForeignFiles` set, the restart notice now says: \"Your deny and ask rules may not be in force in this cloud session: its environment was restarted.\"\n\n**Why**\n\nFiles you did not create through Claude Code are no longer deleted during restore. When that happens, check your permission rules, since the notice warns that rules blocking or asking about actions may not be applied.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}