Under the hood
Useful2 Signal3
Write checks its target path before remote runs and explains what an empty diff means.
What's wrong with this entry?
Anonymous. No account, no email.
What
Write's input schema gained extra fields and its validation now does an asynchronous path check for remote runs that can reject with a new error code. Its descriptions of the returned patch and original file now spell out what an empty diff means and when a file is too large to include.
Details
- Three file tools now declare remote execution support, where none did in the previous build.
- The extra schema fields are added by a shared helper; how that helper builds the machine-routing parameter is not visible in the bundle.
Evidence
remoteExecution: { supported: !0 }
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.239
Remote tool execution is complete but hard-disabled in this build
Both mention execution
-
v2.1.239
The
deviceparameter is hidden from every tool that could run remotelyBoth mention execution
-
v2.1.239
Tools can declare whether they run remotely; Bash is the first, and it is scaffolding
Both mention execution