You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.277,
Bug FixesSection of the release
What
The Edit tool can treat a literal search string containing \uXXXX unicode escape sequences as if it were a regular expression. Before building that regular expression, Claude Code now estimates how long the resulting pattern would be and checks that the escape sequences are well-formed, instead of just testing length and regex validity generically. If this check fails, it now logs a specific message explaining that the \uXXXX-escape search was skipped because the regex engine refused a pattern of a given length, rather than silently returning nothing.
Why
This makes it clearer when and why an edit search involving unicode escapes didn't work, instead of the tool failing silently.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed the Edit tool treating an escaped backslash followed by uXXXX text as a \uXXXX escape, which could make an edit of a non-ASCII…