Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.247,
What probably matters to youSection of the release
auto_open with at_create and after_first_write is in the tool schema but spliced in only when server config enables Artifact type creation.
What
The Artifact tool schema accepts auto_open with values at_create and after_first_write, applying only to a create with type_url and no file_path. It is spliced into the schema only when Artifact type creation is enabled for the account by server-side config, so with no server value the parameter is not offered at all.
Details
Passing it alongside file_path is refused with reason auto_open_with_files; passing it without type_url is an input-validation error.
In 2.1.246 the only auto_open strings in the build were unrelated telemetry reasons, so the parameter itself is new.
Evidence
auto_open: un(["at_create", "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_openat_createafter_first_writetype_url
Since it was published
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up at_create, on Apps.`GET /v1/compliance/activities` with `activity_types[]=claude_chat_created`api/compliance/appssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up at_create, on Apps.
