Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.317,
What probably matters to youSection of the release
Unclear Whether anything in Claude Code offers these rules to you yet is not stated.
What
Claude Code has new code for building standing allow rules, permission rules that let something run without asking each time. A rule can cover a command, a web host or an MCP tool, and is kept narrow. It covers:
Read-only commands.
mkdir, touch, rm, mv and cp with a limited set of flags.
npm test and make targets.
It refuses with a named reason in risky cases, for example when a managed deny rule applies, when you have your own ask rule, when a command is not known to be safe, when a host is not public, or when the path contains a symlink. Rules are saved to your local or project settings with a write that guards against symlinks.
Why
If this is connected to a screen you can use, it changes how you create permanent allow rules, with Claude Code refusing to offer ones that would be unsafe.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether anything in Claude Code offers these rules to you yet is not stated.
