Claude Code v2.1.219 ·
Dangerous-delete detection uses a prebuilt regex
Permission checks for risky delete commands do slightly less work each time, with identical results.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Internal ChangesKind: in v2.1.219,
Internal ChangesSection of the release
What
The PowerShell and cmd delete-command matcher no longer rebuilds its alternation on every call.
Details
- The matcher takes a second parameter and tests against a module-level regex compiled once from the same
rm|remove-item|ri|del|erase alternation - Matching behaviour is unchanged; this removes per-invocation work on a hot permission path
Evidence
rm|remove-item|ri|del|erase
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.219 →
