Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

Artifacts can wait for their first write before opening

Artifacts can hold off opening until real content lands, with auto_open set to after_first_write.

Use it now No documentation found New Features
JSON All of v2.1.247
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.247,
What probably matters to youSection of the release
What

Creating an Artifact from a type can now pass auto_open: "after_first_write", which holds back opening it for you until content actually lands, so you no longer watch an empty page. The pending open is parked per Artifact and flushed by the first successful write, or consumed by a later publish of files. Validation rejects the value when there is nothing to wait for, such as a publish that is itself the first write.

Details
  • The alternative value is at_create, the previous behaviour of opening immediately.
  • No separate flag for auto_open was found; it rides on the existing Artifact type-creation schema.
Evidence

after_first_write

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

Read from
Names in the bundleauto_openafter_first_write

See this entry in the whole of v2.1.247 →

Feedback