Writing over a very large file skips diff computation, so it no longer stalls.
What's wrong with this entry?
Writing over a very large file no longer computes or returns a full structured patch. The tool returns an empty patch and no original file contents, skips the extra git-diff work done in cloud sessions, and passes the raw old and new text straight to the diff-metrics call.
- The size threshold is a fixed build constant, not a setting.
- The skipped cloud-session work is the step reported as
tengu_tool_use_diff_computed.
tengu_tool_use_diff_computed
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.
-
v2.1.227
"Did you mean" file suggestions no longer block on a directory scan
Both mention file tool
-
v2.1.242
PDF reads return the document and page images
Both mention file tool
-
v2.1.248
Edit tool drops two validation branches
Both mention file tool