{"version":"2.1.311","anchor":"artifact-comment-reply-guard-probe-now-runs-concurrently","canonical_anchor":"artifact-comment-reply-guard-probe-now-runs-concurrently","heading":"Saving or deleting project docs goes to classifier review in arbiter mode","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/artifact-comment-reply-guard-probe-now-runs-concurrently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Saving or deleting project docs goes to classifier review in arbiter mode\n\nIn the arbiter permission mode, saving or deleting a project doc is now handed on for classifier review\n\n**Unclear.** Whether the arbiter permission mode is available to ordinary users is not stated.\n\n**What**\n\nWhen Claude Code is in the arbiter permission mode, saving or deleting a project doc now goes through a permission step. A permission mode sets how Claude Code decides whether to ask before acting. The step hands the action on for classifier review, an automatic check of the action, with the reason \"Saving or deleting a project doc requires classifier review.\" Claude Code also records when a project write starts.\n\nSeparately, when replying to comments on an artifact, a check that guards the reply now runs at the same time as a check on whether the page owns its comment threads, instead of after it. It is stopped early if that other check finds a match.\n\n**Why**\n\nIn arbiter mode, changes to project docs no longer go through without an automatic review first.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}