When Claude changes one of Claude Code's own settings files without your approval, the change is held as a proposal instead of being applied. A review screen lists these proposals, and for each one you can:
- accept it, so it takes effect
- discard it
- decide later
A second set of wording covers project settings files used by cloud sessions served from this computer. Those cloud sessions only use a version you have accepted, and the screen marks versions "Not accepted for cloud sessions yet" with a choice to "Accept this version for cloud sessions".
There is also an accept command run from claude. Accepting needs an interactive terminal, and it runs your ConfigChange hooks (commands you set to run when a configuration file changes) against the proposed file. Claude Code refuses to accept a file that is hard-linked, symlinked (a shortcut pointing to another file) or has been tampered with.
Edits Claude makes to its own settings can be kept aside until a person looks at them, and cloud sessions running from your computer will not pick up settings you have not agreed to.
It is not clear what switches the holding of changes on, what the accept command is called, or whether it is available in this build.