{"version":"2.1.281","anchor":"cloud-file-sync-refuses-folders-that-are-too-large-or-overla","canonical_anchor":"cloud-file-sync-refuses-folders-that-are-too-large-or-overla","heading":"Cloud sessions refuse to sync folders that are too large","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-refuses-folders-that-are-too-large-or-overla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud sessions refuse to sync folders that are too large\n\nA new folder_too_large refusal starts a cloud session without the folder's files and lists the largest ones to trim\n\n**What**\n\nWhen you start a cloud or remote session from a folder, Claude Code can upload that folder's files. It now refuses when the folder is too large, with the reason `folder_too_large`:\n\n- The message says: \"This cloud session starts without this folder's files; to sync it next time, remove or ignore what the session does not need (a .gitignore in this folder is honoured).\"\n\n- It lists the largest files, and the refusal line has an extra suffix.\n\n- The session's diagnostic reporting records this reason separately, with the folder's file count and total size.\n\nA folder that overlaps the host's configuration is also no longer offered for sync. Before, sync was offered whenever the folder was readable.\n\n**Why**\n\nThis avoids very large uploads. If you want the folder synced next time, remove or ignore what the session does not need, for example with a `.gitignore` in that folder.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}