{"version":"2.1.295","anchor":"cold-claim-check-skipped-when-a-flag-is-set-home-settings-s","canonical_anchor":"cold-claim-check-skipped-when-a-flag-is-set-home-settings-s","heading":"A project-settings check at cloud worker startup is now sometimes skipped","tier":"internal","area":"Cloud Sessions","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cold-claim-check-skipped-when-a-flag-is-set-home-settings-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### A project-settings check at cloud worker startup is now sometimes skipped\n\nA startup check on whether project settings can be claimed is now skipped in some cases, and settings sync handles files from elsewhere\n\n**Unclear.** What condition makes the project-settings check get skipped is not known.\n\n**What**\n\nWhen a managed cloud worker starts up, Claude Code checks whether the project's settings can be claimed. Previously that check always ran. It is now skipped when a certain condition is set.\n\nSettings syncing also now takes a list of files that came from elsewhere. When the settings in your home folder cannot be read, the step that seeds them now reports that nothing was replaced.\n\n**Why**\n\nThis affects how Claude Code starts on managed cloud workers.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}