Source Intelligence

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.235 Home All releases olderv2.1.234 v2.1.236newer
Claude Code v2.1.235

Artifact tool approvals cannot be swapped to a different target

You'll notice
Useful3 Signal3
Artifacts

An approved artifact tool call can no longer be redirected to a different project or action.

What

Approving an artifact tool call now attaches a hidden marker recording exactly which action and which project were approved. Before the privileged step runs, that marker is read back and must match the action and project actually being executed, otherwise the call fails with asset_target_changed.

Details
  • Covers list_assets, read_page_data, watch, read_db and write_db.
  • The marker is stored as a non-enumerable property and read with Reflect.get, so it cannot be spoofed by ordinary input fields.
  • An input carrying any of the other four consent markers is rejected outright.
  • Unconditional; there is no flag to turn this off.
Evidence

__artifactConsentPin

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.235 →