Your permission mode is re-checked once remote settings load, so startup no longer sticks on the wrong one.
What's wrong with this entry?
At startup the permission mode is sometimes decided before the remote feature-flag cache has loaded, which could settle on the wrong mode. Claude Code now re-resolves the mode once the cache is populated and re-applies it if the answer differs, logging a warning when it does.
- The correction deliberately will not switch you into bypassPermissions when that mode is unavailable, nor into auto mode when the auto-mode gate is off.
- Which mode is ultimately chosen still depends on remote feature-flag configuration.
startup resolved ${e.mode} against an empty GrowthBook cache; re-resolved to ${r.mode}
Strings lifted out of the shipped bundle, so the claim above can be checked against them.