{"version":"2.1.281","anchor":"footer-frame-item-now-opens-artifacts-in-footer-frame-cy","canonical_anchor":"footer-frame-item-now-opens-artifacts-in-footer-frame-cy","heading":"Footer 'frame' item now opens \/artifacts; in-footer frame cycling and dismissing removed","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/footer-frame-item-now-opens-artifacts-in-footer-frame-cy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Footer 'frame' item now opens \/artifacts; in-footer frame cycling and dismissing removed\n\nOpening the footer's frame item now runs `\/artifacts`; cycling and dismissing frames from the footer are gone\n\n**What**\n\nThe footer is the row of items along the bottom of the Claude Code screen. When you select its \"frame\" item and open it, Claude Code now runs the `\/artifacts` command (\"Browse your published and shared artifacts\"). Before, it opened the frame's web address directly.\n\nOther footer behaviour changed with it:\n\n- `footer:next` and `footer:previous` now only move between footer items and no longer step through frames\n\n- `footer:dismiss`, which removed a frame link and showed \"Dismissed \u2026 from this list\", is gone from the footer keys\n\n**Why**\n\nFrames are now reached through the `\/artifacts` list instead of one at a time from the footer. `\/artifacts` only works where artifact policy allows artifacts, so this path depends on that policy too.\n\n- Area: Artifacts\n- Names: `\/artifacts`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}