{"version":"2.1.260","anchor":"artifact-auto-open-is-now-suppressed-for-remote-control-sess","canonical_anchor":"artifact-auto-open-is-now-suppressed-for-remote-control-sess","heading":"Artifact auto-open is now suppressed for remote-control sessions","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/artifact-auto-open-is-now-suppressed-for-remote-control-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Artifact auto-open is now suppressed for remote-control sessions\n\nArtifacts no longer auto-open a browser tab when you're driving Claude Code remotely from mobile or web.\n\nArtifact auto-open is now suppressed when the session's `messageClientPlatform` is `ios`, `android`, `web_claude_ai`, or `desktop_app`, via a new mode called `auto_open_skipped_remote_control`. The skipped artifact's slug is recorded in a new `remoteControlSkippedSlugs` set, and its deferred-surface entry is kept around instead of cleared, so it can retry surfacing later instead of force-opening a browser tab while Claude Code is being driven from a mobile, web, or desktop remote-control client. This path fires unconditionally, with no experiment flag gating it.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}