{"version":"2.1.288","anchor":"audioplay-clips-now-carry-pluginstorageid","canonical_anchor":"audioplay-clips-now-carry-pluginstorageid","heading":"Plugin audio clips are now checked against the plugin's own storage","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/audioplay-clips-now-carry-pluginstorageid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Plugin audio clips are now checked against the plugin's own storage\n\nWhen a plugin plays an audio clip, Claude Code now checks the clip's address using the plugin's storage ID as well as its name\n\n**Unclear.** What the check on the clip's address actually allows or blocks is not established.\n\n**What**\n\nWhen a plugin plays an audio clip with `$.audio.play`, Claude Code checks the clip's address first. That check used to receive only the plugin's name. It now also receives the plugin's storage ID.\n\n**Why**\n\nAudio from a plugin is now tied to that plugin's own storage.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}