{"version":"2.1.247","anchor":"artifacts-can-wait-for-their-first-write-before-opening","canonical_anchor":"artifacts-can-wait-for-their-first-write-before-opening","heading":"Artifacts can wait for their first write before opening","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifacts-can-wait-for-their-first-write-before-opening","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifacts can wait for their first write before opening\n\nArtifacts can hold off opening until real content lands, with auto_open set to after_first_write.\n\n**What**\n\nCreating 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.\n\n**Details**\n\n- The alternative value is `at_create`, the previous behaviour of opening immediately.\n- No separate flag for `auto_open` was found; it rides on the existing Artifact type-creation schema.\n\n**Evidence**\n\n`after_first_write`\n\n- Area: Artifacts\n- Names: `auto_open`, `after_first_write`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}