{"version":"2.1.227","anchor":"watching-an-artifact-from-a-remote-session-now-wakes-it-inst","canonical_anchor":"watching-an-artifact-from-a-remote-session-now-wakes-it-inst","heading":"Watching an artifact from a remote session now wakes it instead of streaming","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/watching-an-artifact-from-a-remote-session-now-wakes-it-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Watching an artifact from a remote session now wakes it instead of streaming\n\nIn remote sessions, watching an artifact wakes you on publish instead of streaming live updates.\n\n**What**\n\nWith `CLAUDE_CODE_REMOTE` set, the artifact `watch` action no longer opens a live-update connection. It registers a durable wake so the session is woken with a new turn the next time the artifact is published, and nothing is streamed in the meantime, so the artifact has to be re-read on wake.\n\n**Details**\n\n- The `status` action lists these subscriptions under a `durable_wake` entry with the trigger id and the time it has been watching from.\n- Failures name the cause: a ceiling of 10 wake triggers, client egress policy, or missing credentials.\n\n**Evidence**\n\n`Durable wake subscription registered \u2014 this session will be woken by a new turn when the artifact is next published. No updates are streamed; re-read the artifact on wake.`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}