{"version":"2.1.293","anchor":"cloud-upload-message-for-unreadable-settings-reworded","canonical_anchor":"cloud-upload-message-for-unreadable-settings-reworded","heading":"Clearer wording when settings could not be read before a cloud upload","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-upload-message-for-unreadable-settings-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Clearer wording when settings could not be read before a cloud upload\n\nThe notice about unreadable Read rules or sandbox settings now says uncommitted files are left out of the upload to the cloud session\n\n**What**\n\nWhen you start a cloud session, Claude Code uploads your project. If it could not read your Read rules (settings that control which files Claude may read) or your sandbox settings (the limits on what Claude's commands can touch), it shows a notice. That notice now says: \"uncommitted file contents are left out of this upload; the cloud session starts from what is committed.\" It used to say uncommitted file contents stay on this machine for this session.\n\n**Why**\n\nThe new wording says plainly what you will see in the cloud: only work you have committed, without unsaved changes from your computer.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}