{"version":"2.1.283","anchor":"directory-sync-reports-when-a-cloud-sessions-file-store-is","canonical_anchor":"directory-sync-reports-when-a-cloud-sessions-file-store-is","heading":"Directory sync tells you when a cloud session's file store is full","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/directory-sync-reports-when-a-cloud-sessions-file-store-is","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Directory sync tells you when a cloud session's file store is full\n\nWhen a cloud session's file store fills up, directory sync now tells you and Claude that further changes stay in the cloud\n\n**Unclear.** Whether cloud directory sync is available to everyone is not known.\n\n**What**\n\nDirectory sync keeps a cloud session's copy of your project in step with your machine. Each cloud session has a file store with a limit on uploads and size. When the environment has used up its share of that store, or the store refuses an upload, Claude Code now sends a notice. Before, this was only recorded internally and nobody was told.\n\n- You are told that Claude's further changes stay in the cloud session and are not synced to your machine.\n\n- Claude is told that nothing it changes will reach your machine through sync, and to tell you so plainly.\n\nThe same update shortens the message shown after sync gives up waiting and simplifies the restore messages, removing the \"last turn\" restore case. The longer \"File sync stopped for this session\" notice to Claude, which said the synced copy had been moved into the session's trash, is gone.\n\n**Why**\n\nIf you use cloud sessions with directory sync, you now learn when later work is stuck in the cloud instead of assuming it reached your machine.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}