{"version":"2.1.280","anchor":"new-created-empty-never-filled-state-for-cloud-session-fo","canonical_anchor":"new-created-empty-never-filled-state-for-cloud-session-fo","heading":"New \"created empty, never filled\" state for cloud-session folder sync","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-created-empty-never-filled-state-for-cloud-session-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New \"created empty, never filled\" state for cloud-session folder sync\n\nCloud session folder sync now reports when a session was created empty and never got its first upload\n\n**What**\n\nWhen attaching to a cloud session for directory sync, Claude Code can now detect a session that was created empty on the server and never received its first upload of files. Instead of silently treating this as if there were no files, it now reports a specific stopped reason and suggests starting a new cloud session from the folder.\n\n**Why**\n\nThis makes a previously confusing, silent failure into a clear, actionable message, so an empty never-synced session doesn't look like missing or lost data.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}