{"version":"2.1.269","anchor":"edit-tool-result-can-now-be-staged-for-review-pending-sett","canonical_anchor":"edit-tool-result-can-now-be-staged-for-review-pending-sett","heading":"Edit tool result can now be 'staged for review' pending settings owner approval","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/edit-tool-result-can-now-be-staged-for-review-pending-sett","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Edit tool result can now be 'staged for review' pending settings owner approval\n\nEdit tool results can now report a change as 'staged for review' instead of applied, when settings files require owner approval\n\n**What**\n\nThe Edit tool can now mark its result as `staged`. When that happens, instead of confirming the edit was made, Claude Code reports that the file was NOT modified because changes to Claude Code's own settings files are held for the computer owner to review, via `\/settings-review`.\n\n**Why**\n\nThis prevents Claude from silently changing Claude Code's own settings files and instead requires the computer's owner to explicitly approve those changes through `\/settings-review`, adding a safety check around self-modifying configuration.\n\n- Area: Settings\n- Names: `\/settings-review`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}