{"version":"2.1.280","anchor":"new-project-directory-cloud-sync-coverage-checker","canonical_anchor":"new-project-directory-cloud-sync-coverage-checker","heading":"New project-directory cloud-sync coverage checker","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-project-directory-cloud-sync-coverage-checker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New project-directory cloud-sync coverage checker\n\nNew checker determines whether a project directory's files are actually reachable by cloud-session sync\n\n**What**\n\nClaude Code has a new internal module that checks whether a project directory's files are actually reachable and kept in sync by its cloud-session configuration. It walks symbolic links, checks whether paths are contained within the home directory, and checks for network shares, then classifies problems it finds as `root_linked`, `inside_home`, or `unexamined` (with reasons like too many entries, unreadable, or on a network share).\n\nIt also defines a fixed set of folder names, such as `agent-memory`, `cache`, `projects`, `mcp-discovery-cache`, `plugins`, and `cowork_plugins`, that are treated as Claude Code's own configuration tree for the purposes of this sync check.\n\n**Why**\n\nThis helps identify cases where a project's files won't actually be captured by cloud-session sync, for example because they're symlinked outside the expected location or live on a network share, so problems can be flagged rather than silently missing data.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}