Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.233 Home All releases ←olderv2.1.232 v2.1.234newer→
Claude Code v2.1.233

Artifact watch priming, failure text and resume stand-down

Not switched on
Useful2 Signal4
Artifacts

When artifact watching turns on, Claude is told to re-read the artifact before editing it.

Watch priming messages and per-case failure text exist but only fire when artifact watching is enabled.

What

When a watch is armed, the session injects a message telling the model it is watching that artifact and must re-read it before editing or republishing, and prints a notification. Each way arming can fail now has its own message.

Details
  • Failure reasons with distinct text: artifact not found, no subscription token, boot failed, sandbox egress denied, watch cap reached, websocket open error, and remote sessions.
  • Resuming a transcript that started with a watch injects an explicit notice that the watch does not carry into the new session.
  • Startup outcomes are logged as artifact_watch_startup with reasons including fetch_gate and arm_error.
Evidence

--watch-artifact is not available in remote sessions., The watch started with claude --watch-artifact earlier in this transcript does not carry into this session

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.233 →