A hidden flag lets a session watch an artifact for new versions and comments, with an option to disarm auto-reply.
What's wrong with this entry?
A session can now watch a Claude artifact by id or claude.ai URL and be notified when new versions and comments arrive. --watch-artifact-no-autoreact starts the same watch with auto-reply disarmed. Both are registered hidden, so they do not show up in --help. Startup refuses them in non-interactive, print, --sdk-url, --init-only and redirected sessions, and in sessions attached to a remote environment, each with its own error text.
- A malformed value produces an artifact-id/URL error; a URL belonging to a different environment is rejected against the one you are signed in to.
- Neither flag string appears in the previous build.
claude --watch-artifact https://claude.ai/...Error: --watch-artifact is not available in sessions attached to a remote environment \u2014 run it in a plain local session
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.234
--watch-artifactnow fails fast in remote sessionsBoth 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