{"version":"2.1.247","anchor":"auto-open-parameter-on-the-artifact-tool","canonical_anchor":"auto-open-parameter-on-the-artifact-tool","heading":"auto_open parameter on the Artifact tool","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/auto-open-parameter-on-the-artifact-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### `auto_open` parameter on the Artifact tool\n\nThe Artifact tool's auto_open option only appears if server-side config enables Artifact type creation for you.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Passing it alongside `file_path` is refused with reason `auto_open_with_files`; passing it without `type_url` is an input-validation error.\n- In 2.1.246 the only `auto_open` strings in the build were unrelated telemetry reasons, so the parameter itself is new.\n\n**Evidence**\n\n`auto_open: un([\"at_create\", \"after_first_write\"])`\n\n- Area: Artifacts\n- Names: `auto_open`, `at_create`, `after_first_write`, `type_url`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}