{"version":"2.1.288","anchor":"artifact-system-prompt-device-apis-now-tied-to-runtime-capa","canonical_anchor":"artifact-system-prompt-device-apis-now-tied-to-runtime-capa","heading":"Artifact instructions allow device features when your account supports them","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/artifact-system-prompt-device-apis-now-tied-to-runtime-capa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Artifact instructions allow device features when your account supports them\n\nClaude's artifact instructions now allow device features such as motion sensors only when you have that capability and the page declares it\n\n**What**\n\nArtifacts are web pages that Claude writes for you. Claude's instructions for writing them list device features that the page frame refuses, and motion sensors are now on that list. Before, the instructions simply said not to build features on those devices.\n\nNow Claude may build on one of them only when you have a runtime capability for that device, meaning your setup actually supports it, and the page declares that it uses it. The instructions name a skill to use for this. The sentence about keeping the screen awake is now separate.\n\n**Why**\n\nThis changes the artifacts Claude writes. Pages can now use some device features where they will work, instead of avoiding them entirely.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}