{"version":"2.1.287","anchor":"staging-files-into-a-sandboxed-home-directory-uploadshom","canonical_anchor":"staging-files-into-a-sandboxed-home-directory-uploadshom","heading":"Cloud sessions can place files into a protected home folder","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/staging-files-into-a-sandboxed-home-directory-uploadshom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cloud sessions can place files into a protected home folder\n\nIn cloud sessions, files can now be placed into a home folder under \/uploads\/.home, never overwriting existing files\n\n**Unclear.** It is not clear which setting switches home files on.\n\n**What**\n\nIn a cloud session (one running on Anthropic's servers), Claude Code could previously only use a read-only `\/uploads\/` folder and an `\/outputs\/` folder. It can now also place files into a home folder at `\/uploads\/.home`, under strict rules:\n\n- It never replaces a file that already exists\n\n- File names are checked strictly\n\n- Files are written in a way that guards against being redirected elsewhere\n\n- It works only when a setting for home files is on, and fails with \"the flag for home files has not loaded\" if that setting is not ready yet\n\n`add_directory` now refuses folders under `\/uploads\/.home\/`. When one turn hands over to the next, files named in a tool call (a request Claude makes to use one of its tools) are now copied across.\n\n**Why**\n\nCloud sessions can now put files where programs expect a home folder, without risking files that are already there.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}