{"version":"2.1.283","anchor":"file-listing-no-longer-skips-nested-paths-for-rootonly-sourc","canonical_anchor":"file-listing-no-longer-skips-nested-paths-for-rootonly-sourc","heading":"Cloud sync no longer limits root-only folders to top-level files","tier":"notice","area":"File Reading","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-listing-no-longer-skips-nested-paths-for-rootonly-sourc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud sync no longer limits root-only folders to top-level files\n\nThe rootOnly mode is removed: nested files are no longer skipped and the \"files stay in the cloud\" warning is gone\n\n**Unclear.** Which Claude Code feature uses root-only sources is not established.\n\n**What**\n\nWhen a cloud session edits files, Claude Code syncs them back to a folder on your machine. Some folder setups used a restricted `rootOnly` mode that only handled files directly in the folder, not in subfolders. That restriction is removed:\n\n- The file reading step no longer skips any path inside a subfolder as \"unreadable\" for root-only sources.\n\n- The by-name backend no longer has a `rootOnly` mode. Before, nested paths in that mode failed and the sync round was skipped as `anchor_degraded`, with the warning \"Files Claude changed in the cloud were not placed on this machine and stay in the cloud session\". That warning is gone.\n\n- The directory operation that always reported unavailable for root-only backends now tries to run for them. Only the `by_name` backend still reports unavailable.\n\n**Why**\n\nFiles in subfolders that were previously skipped may now be read and placed on your machine. The case where cloud edits quietly stayed in the cloud now either works or fails in some other way.\n\n- Area: File Reading\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}