A new --watch-artifact flag follows a claude.ai artifact for new versions and comments, but needs account access.
Artifact watching is fully built behind the tengu_slate_lantern gate, which falls back off, so most accounts see a refusal message.
tengu_slate_lantern On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.233: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new startup flag takes a claude.ai artifact id or URL and watches it for new versions and comments during the session, telling Claude which artifact is the current one of interest. It needs the tengu_slate_lantern gate (fallback off); without it you get "Artifact watching is not available for this account yet."
- A hidden
--watch-artifact-no-autoreactvariant arms the watch without automatic comment replies. - Both flags are hidden from
claude --help, though they parse on every build, and both were added to the lists of flags that take a value and get forwarded. - Rejected in non-interactive and print sessions, and in sessions attached to a remote environment; the id is validated against the signed-in environment.
- Arming prints a feedback line built around "Watching artifact".
claude --watch-artifact https://claude.ai/public/artifacts/<id>Watch a Claude artifact (id or URL) in this session and hear about new versions and comments
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