{"version":"2.1.227","anchor":"startup-notice-when-a-cloud-session-could-not-be-bound-to-yo","canonical_anchor":"startup-notice-when-a-cloud-session-could-not-be-bound-to-yo","heading":"Startup notice when a cloud session could not be bound to your machine","tier":"soon","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/startup-notice-when-a-cloud-session-could-not-be-bound-to-yo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Startup notice when a cloud session could not be bound to your machine\n\nYou could get a startup notice when a cloud session could not be bound to your machine.\n\n**What**\n\nIf a cloud session starts and the server returns no device id, the session now queues a plain-language notification instead of staying silent. The text is the fixed prefix `Not bound to this machine (local tools off): ` plus a reason. It only appears on the cloud-session path and only when `tengu_violin_wood` is on.\n\n**Details**\n\n- Reasons include \"this account has reached its device limit\", \"no stored claude.ai login on this machine (run \/login)\", \"the server refused it (server-side bind flag likely off)\", and \"the device feature flag was off or unreadable at create time\".\n\n**Evidence**\n\n`the device feature flag was off or unreadable at create time`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.227; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}