{"version":"2.1.268","anchor":"new-artifact-wake-subscription-failure-reason-session-devic","canonical_anchor":"new-artifact-wake-subscription-failure-reason-session-devic","heading":"New artifact wake-subscription failure reason: session_device_bound","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-artifact-wake-subscription-failure-reason-session-devic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### New artifact wake-subscription failure reason: session_device_bound\n\nNew error explains why artifact wake subscriptions fail on desktop-bound cloud sessions\n\n**What**\n\nArtifact \"wake subscriptions\" (which let a session be woken up by activity on an artifact) now report a specific new failure reason, `session_device_bound`, when the cloud session is tied to the desktop that started it, such as through Cowork or `claude --cloud`. This happens because of a trusted-device check, and it's now fully wired up: parsed from the server's response, shown to the user with a specific message, and checked at another point in the code.\n\n**Why**\n\nUsers running a desktop-bound cloud session will now get a clear explanation of why wake subscriptions don't work for them, and know that retrying won't help, while publishing and reading artifacts are unaffected.\n\n- Area: Artifacts\n- Names: `session_device_bound`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}