Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.233 Home All releases ←olderv2.1.232 v2.1.234newer→
Claude Code v2.1.233

Windows Bash argument scanning sees through --flag=value and NT device paths

You'll notice
Useful2 Signal1
Windows

Windows command scanning now unwraps flag=value arguments and spots NT object-manager paths.

What

On Windows, the check that spots network and device paths in Bash command arguments now strips --flag= and -f= prefixes repeatedly and re-checks what is left, and recognises \??\ NT object-manager paths. Off entirely on other platforms.

Details
  • Path checks in Read, Edit and NotebookEdit, plus the file-path display component, moved from ad-hoc \\ / // prefix tests to shared helpers that also cover /net/<host> autofs paths.
  • NotebookEdit lost its shortcut that accepted UNC paths without further checks, so those paths now go through the .ipynb extension check like any other.
Evidence

WAd = /^--?[A-Za-z0-9][\w-]*=/

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.233 →