{"version":"2.1.304","anchor":"home-directory-cloud-binding-message-reworded","canonical_anchor":"home-directory-cloud-binding-message-reworded","heading":"Clearer message when a folder can't be used for cloud sessions","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/home-directory-cloud-binding-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Clearer message when a folder can't be used for cloud sessions\n\nThe message for a folder that can't be bound to cloud sessions now covers home folders, hidden folders and repositories rooted there\n\n**What**\n\nThe reason Claude Code gives when a folder cannot be bound for cloud sessions has been rewritten. It now says the folder is never bound because it, or its repository, is your home directory, sits in a hidden folder there, or is another such place. It suggests using a project folder of its own, such as `~\/code\/my-app`.\n\nBefore, the message only mentioned launching from the home directory, above it, or inside a checkout rooted there.\n\n**Why**\n\nThe message now names more of the places that are refused and gives a concrete example of where to start `claude --cloud` instead.\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"}