{"version":"2.1.247","anchor":"artifact-create-results-say-when-the-artifact-was-opened","canonical_anchor":"artifact-create-results-say-when-the-artifact-was-opened","heading":"Artifact create results say when the Artifact was opened","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-create-results-say-when-the-artifact-was-opened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact create results say when the Artifact was opened\n\nArtifact results now record whether the Artifact opened at creation or after the first write.\n\n**What**\n\nA created-from-type Artifact result now carries an `auto_open` field of `\"at_create\"` or `\"after_first_write\"`, telling the model at which point the Artifact was shown to you.\n\n**Details**\n\n- Auto-open can still be switched off per environment with `CLAUDE_CODE_ARTIFACT_AUTO_OPEN`, logged as `auto_open_skipped_env`.\n- Other recorded skip reasons cover background runs, teammate sessions, remote sessions, the desktop pane and the VS Code pane.\n\n**Evidence**\n\n`auto_open: un([\"at_create\", \"after_first_write\"]).optional(),`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}