{"version":"2.1.246","anchor":"cloud-sessions-started-from-your-home-directory-cannot-bind-","canonical_anchor":"cloud-sessions-started-from-your-home-directory-cannot-bind-","heading":"Cloud sessions started from your home directory cannot bind a device","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-sessions-started-from-your-home-directory-cannot-bind-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud sessions started from your home directory cannot bind a device\n\nStarting a cloud session in your home directory now blocks device linking and tells you to use a project folder.\n\n**What**\n\nLaunching a cloud session from your home directory now blocks linking this machine to it, with a message telling you to run `claude --cloud` from a project folder of its own.\n\n**Details**\n\n- The new refusal reason `launched_from_home` is checked first, before the existing network, account and device-proof checks.\n- Both the reason and its message are new in this build; nothing turns the check off.\n\n**Evidence**\n\n`launched_from_home`\n\n- Area: Cloud Sessions\n- Names: `claude --cloud`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}