{"version":"2.1.286","anchor":"artifact-comment-writepublish-unasked-telemetry-and-comme","canonical_anchor":"artifact-comment-writepublish-unasked-telemetry-and-comme","heading":"Artifact comment writes get their own permission path","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/artifact-comment-writepublish-unasked-telemetry-and-comme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Artifact comment writes get their own permission path\n\nArtifact comments get a separate commentWrite permission, allowed in turns not started by a human, and unasked writes are now tracked\n\n**Unclear.** What turns this permission on, and which feature it belongs to, is not known.\n\n**What**\n\nArtifacts are documents Claude can create and share, and they can have comments. Writing a comment now has its own permission flag, `commentWrite`, instead of relying only on `routineWrite`.\n\n- The permission check for artifact writes now passes `commentWrite` and records approval for comment writes separately from routine writes.\n\n- When a turn was not started by a human, `commentWrite` set to true is let through by the same branch that already allowed `routineWrite`.\n\n- Two new telemetry events, usage data sent back to Anthropic, fire when a comment is written or published without being asked for.\n\n- Separately, the options used for model requests gain `accessFallbackModel`.\n\n**Why**\n\nComments on artifacts can now be written in turns that no person started, such as automated runs. Comments written without being asked for are now counted.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}