{"version":"2.1.269","anchor":"artifacts-can-now-be-marked-authored-by-others","canonical_anchor":"artifacts-can-now-be-marked-authored-by-others","heading":"Artifacts can now be marked 'authored by others'","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/artifacts-can-now-be-marked-authored-by-others","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Artifacts can now be marked 'authored by others'\n\nArtifacts can now be flagged as 'authored by others' when Claude isn't their sole author\n\n**What**\n\nArtifacts (files Claude Code produces as a distinct output) can now be marked with an `authoredByOthers` flag. A related check now treats an artifact as not fully Claude-owned if it has this flag, alongside the existing reasons: `probeFailed`, `cowritten`, or `typeLocked`.\n\n**Why**\n\nThis lets Claude Code correctly track and handle artifacts that weren't entirely created by Claude, presumably affecting how such artifacts can be edited or treated compared to fully Claude-authored ones.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}