You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.275,
ImprovementsSection of the release
Unclear The finding does not say what the different treatment actually looks like for the user.
What
Artifact permission logic gains two new fields, invitedByOtherOrg and canWrite, computed by probing the artifact's role and mode. These feed directly into the write-consent decision, so Claude Code can now tell apart an artifact you own from one where someone in a different organization gave you editor access.
Why
This lets Claude Code apply different consent handling when writing to an artifact you don't fully own but were invited to edit by another org, rather than treating all editable artifacts the same way.
