You'll notice
No documentation found
Artifact write permissions now separate editor access granted by another org from actual ownership
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.
Names in the bundleinvitedByOtherOrgcanWrite
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what the different treatment actually looks like for the user.