{"version":"2.1.246","anchor":"write-validates-its-target-path-before-a-remote-run-and-expl","canonical_anchor":"write-validates-its-target-path-before-a-remote-run-and-expl","heading":"Write validates its target path before a remote run, and explains empty diffs","tier":"internal","area":"Remote Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/write-validates-its-target-path-before-a-remote-run-and-expl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Write validates its target path before a remote run, and explains empty diffs\n\nWrite checks its target path before remote runs and explains what an empty diff means.\n\n**What**\n\nWrite'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.\n\n**Details**\n\n- Three file tools now declare remote execution support, where none did in the previous build.\n- The extra schema fields are added by a shared helper; how that helper builds the machine-routing parameter is not visible in the bundle.\n\n**Evidence**\n\n`remoteExecution: { supported: !0 }`\n\n- Area: Remote Execution\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}