Starting with --watch-artifact in a remote session now errors immediately and tells you to run it locally.
What's wrong with this entry?
Starting with --watch-artifact from a remote session errors immediately instead of trying to subscribe, and the message points you at running it locally. The explanation given to the model was rewritten to note that publishing and reading comments still work.
Error: --watch-artifact isn't supported yet from remote sessions \u2014 run it in Claude Code on your own machine
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.233
Permission rules now apply to artifacts fetched without a prompt
Both mention watch
-
v2.1.236
Artifact watch text now says when comment replies are not armed
Both mention watch
-
v2.1.238
Artifact watches are described as paused, not stopped
Both mention watch