Approving settings-file edits from the desktop app's permission card is still off
The code that records a desktop-app approval of a settings-file edit is now filled in, but a check that always says no keeps every edit going to /settings-review
Nothing to try yetNo documentation foundIn Development
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
DesktopArea: what it touches
In DevelopmentKind: in v2.1.282,
What probably matters to youSection of the release
What
When Claude tries to edit one of Claude Code's own settings files, the edit either applies after you approve it on the desktop app's permission card (the approval prompt the app shows) or is held for review in /settings-review. Which one happens depends on whether the desktop app has confirmed your approval.
The part that records that confirmation used to be empty. It now stores the tool name, the file path and a fingerprint of the content being written. Both recording and reading the confirmation also depend on a new check that always answers no, so the confirmation is never treated as given. Edits to settings files still go to /settings-review and are not applied from the permission card.
Why
This is the unfinished part of letting desktop users approve settings changes straight from the permission card. It is switched off in the code itself, not by a remote setting, so only a new build can turn it on.
