{"version":"2.1.233","anchor":"live-artifacts-ask-the-runtime-for-their-write-surface-up-fr","canonical_anchor":"live-artifacts-ask-the-runtime-for-their-write-surface-up-fr","heading":"Live artifacts ask the runtime for their write surface up front","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/live-artifacts-ask-the-runtime-for-their-write-surface-up-fr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Live artifacts ask the runtime for their write surface up front\n\nLive artifacts load their write access once at startup, so the first edit feels faster.\n\n**What**\n\nAll three artifact templates now request the artifact namespace once at load through `claude.use('artifact')` and cache it, instead of looking it up lazily on each edit, so the first edit rarely waits.\n\n**Details**\n\n- Falls back to the old lazy `claude.artifact || claude.self` lookup when `claude.use` is not a function.\n- A new pending state covers the window between asking and answering: edits are tracked as if the document were live, and the status is not prematurely set to `Local only`. When the request resolves the template either saves the pending edits or reports `Local only`.\n- Off in this build; the templates only persist on live documents where the runtime grants the artifact capability.\n\n**Evidence**\n\n`Ask for the namespace at load so the first edit rarely waits on it.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}