You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What
When you answer a permission prompt with "always allow", Claude Code turns your answer into a rule and saves it to a settings file. It now scans the rule first. In these cases the rule applies only to the current session and is not saved:
The rule looks like it contains a secret, such as a password or API key
The rule would be saved to .claude/settings.local.json and git tracks that file
The scan itself fails
Each case shows its own notice, for example "Allowed for this session only. The rule looks like it contains a secret, so it isn't saved to settings." Before, every rule was saved.
Why
Passwords and API keys no longer end up in settings files that get committed to a git repository and shared. If a rule you expected to keep is not remembered next time, one of these notices explains why.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed .claude/settings.local.json not being ignored globally when the folder became a git repository later, or on a new machine
