{"version":"2.1.242","anchor":"live-artifact-rooms-ship-complete-but-can-never-switch-on-in","canonical_anchor":"live-artifact-rooms-ship-complete-but-can-never-switch-on-in","heading":"Live artifact rooms ship complete but can never switch on in this build","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/live-artifact-rooms-ship-complete-but-can-never-switch-on-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Live artifact rooms ship complete but can never switch on in this build\n\nLive rooms on artifacts, with messages and consent, are complete but can never turn on here.\n\n**What**\n\nThe whole live-room feature is present: joining a room when you publish, room event notifications, sending messages of up to 4 KiB on a topic, and per-artifact consent before joining. The availability check reads a null client, so it always answers no, and the room instructions and schema are left out of the artifact tool description this build assembles.\n\n**Details**\n\n- Artifact types are gated separately, by a snapshot taken when the tool schema is built, with independent switches for listing types, creating them and browsing the catalogue.\n- That snapshot is computed from the shape of the server-provided schema plus feature checks, so which type actions a session sees is decided server-side.\n\n**Evidence**\n\n`return null?.isArtifactRoomEnabled() === !0;`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}