In remote sessions, watching an artifact wakes you on publish instead of streaming live updates.
What's wrong with this entry?
With 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.
- The
statusaction lists these subscriptions under adurable_wakeentry with the trigger id and the time it has been watching from. - Failures name the cause: a ceiling of 10 wake triggers, client egress policy, or missing credentials.
Durable wake subscription registered — 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.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.