{"version":"2.1.277","anchor":"artifacts-gain-a-live-room-join-declaration-and-stricter-op","canonical_anchor":"artifacts-gain-a-live-room-join-declaration-and-stricter-op","heading":"Artifacts gain a live-room join declaration and stricter \"open\" tool semantics","tier":"internal","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifacts-gain-a-live-room-join-declaration-and-stricter-op","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifacts gain a live-room join declaration and stricter \"open\" tool semantics\n\nArtifacts get a live-room join option and clearer rules for when to use \"open\" versus publish\/create\n\n**What**\n\nThe description text for artifact tools (used for things like documents, slides, or interactive content generated during a session) now covers a new `room` declaration: joining an artifact's live room means viewer page events arrive back as notifications, and any outbound sends from the artifact need approval first.\n\n- The guidance also tightens when the `open` action should be used versus when a publish or create call has already displayed the artifact, to avoid redundant opens.\n\n- It adds a note that a slide deck built for email or as an attachment, when made from the Slides type, downloads as a `.pptx` or PDF file.\n\n**Why**\n\nThis gives the artifact tools clearer rules for interactive, live-updating artifacts and for exporting a deck in a usable file format, reducing confusion about which action to call when.\n\n- Area: Artifact Publish\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}