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

Claude Code v2.1.232 ·

Output files named by sort, uniq, cp and mv flags now count as writes

Output flags on sort, cp and mv now count as writes, so those files need write permission.

You'll notice New Features
JSON All of v2.1.232
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PermissionsArea: what it touches
New FeaturesKind: in v2.1.232,
What probably matters to youSection of the release
What

Bash permission checks now treat a file named by an output flag as something being written, not read. sort -o out.txt, sort -T dir, and the -t target of cp and mv go through write permission first, and a deny stops the whole command.

Details
  • The analyser carries a table of which flags take a value and which of those values are write targets: sort: { valueLetters: "otkST", writeLetters: "oT" }, uniq: { valueLetters: "fsw", writeLetters: "" }, plus the -t form for cp and mv.
  • uniq has no write letters, so its -f, -s and -w values are consumed as flag arguments rather than mistaken for paths.
  • Previously every path in these commands was analysed as a read.
Evidence

sort: { valueLetters: "otkST", writeLetters: "oT" }

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.232 →

Feedback