{"version":"2.1.283","anchor":"new-refusal-reason-when-a-cloud-session-holds-none-of-this-d","canonical_anchor":"new-refusal-reason-when-a-cloud-session-holds-none-of-this-d","heading":"New message suggests a fresh cloud session when this machine cannot sync files into one","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-refusal-reason-when-a-cloud-session-holds-none-of-this-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### New message suggests a fresh cloud session when this machine cannot sync files into one\n\nWhen a cloud session holds none of this folder's files and this machine cannot sync them, Claude Code suggests starting a new one\n\n**Unclear.** The exact situation that triggers this message is not settled.\n\n**What**\n\nClaude Code can now refuse with a new reason: the cloud session holds none of this project folder's files, and this machine cannot sync them into it. The message tells you to start a new cloud session from this folder instead. A new session begins with a copy of the files, either taken from GitHub or uploaded once.\n\n**Why**\n\nYou get a clear next step instead of a sync failure with nowhere to go.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}