{"version":"2.1.246","anchor":"read-write-and-edit-now-declare-remote-execution-support","canonical_anchor":"read-write-and-edit-now-declare-remote-execution-support","heading":"Read, Write and Edit now declare remote execution support","tier":"notice","area":"Remote Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/read-write-and-edit-now-declare-remote-execution-support","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Read, Write and Edit now declare remote execution support\n\nRead, Write and Edit can now run on another machine, not just Bash.\n\n**What**\n\nIn the previous build only Bash could be routed to another machine. Read, Write and Edit now each declare remote execution support, and Edit's validation grew a remote-aware branch: when the call is remote and the file is missing, it answers \"does not exist on this machine, so nothing was changed.\" instead of offering the local \"Did you mean ...?\" suggestion.\n\n**Details**\n\n- Edit also gained a pre-check that returns error code 15 on failure, and a hook that suppresses all permission updates.\n- The three file tools' input schemas each gained a spread of extra fields from a shared helper whose contents are not visible in the bundle.\n- Nothing gates the descriptor itself; ordinary local use is unaffected.\n\n**Evidence**\n\n`remoteExecution: { supported: !0 },`\n\n- Area: Remote Execution\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 5\/5"}