{"version":"2.1.269","anchor":"artifact-edit-target-checks-now-track-whether-the-artifact-i","canonical_anchor":"artifact-edit-target-checks-now-track-whether-the-artifact-i","heading":"Artifact edit-target checks now track whether the artifact is \"foreign\"","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifact-edit-target-checks-now-track-whether-the-artifact-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifact edit-target checks now track whether the artifact is \"foreign\"\n\nArtifact edit checks now also report whether an artifact is 'foreign'\n\n**What**\n\nThe internal check that decides whether an artifact page can be edited for auto-reply purposes now also returns a `foreign` flag, wherever it returns its editable\/html result. An artifact counts as foreign if it was authored by someone else, the current user's role isn't owner, it's publicly readable, it was co-written, or its type is locked.\n\n**Why**\n\nThis gives the code a clear signal for distinguishing artifacts the current user doesn't fully control, likely feeding into decisions about when Claude Code can safely edit an artifact automatically.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}