Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

project_write now tells Claude to use the path where it read or wrote a file

project_write's error and local_path guidance now tell Claude to give the original path of a file it read or wrote, not a shell-made copy

Group of 2 You'll notice Improvements
JSON All of v2.1.317
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release

What

Claude writes project documents with the project_write tool. The tool now gives Claude extra guidance about which file path to use. Both additions appear only when a certain condition holds. The findings do not say what that condition is.

  • Read-first error: Claude has to read a file before writing it. The error Claude gets for a file it has not read used to end with "or pass its text as content." It can now add another sentence. If the file is an unchanged copy of a file Claude wrote with a tool, Claude should pass the path where it wrote that file.
  • local_path guidance: the description of the tool's local_path input now adds a note. Claude should give the path where it read or wrote the file, not the path of a copy that a shell command made.

Why

In practice, Claude is steered away from copying a file with a shell command and uploading the copy. It uses the original file it already worked with instead, which helps the existing read-before-write check succeed.

See this entry in the whole of v2.1.317 →

Feedback