Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.233 ·

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

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

You'll notice Improvements
JSON All of v2.1.233
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
WindowsArea: what it touches
ImprovementsKind: in v2.1.233,
ImprovementsSection of the release
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.

See this entry in the whole of v2.1.233 →

Feedback