{"version":"2.1.248","anchor":"read-before-write-guard-relaxed-for-remotely-served-calls","canonical_anchor":"read-before-write-guard-relaxed-for-remotely-served-calls","heading":"Read-before-write guard relaxed for remotely served calls","tier":"notice","area":"File Editing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/read-before-write-guard-relaxed-for-remotely-served-calls","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Read-before-write guard relaxed for remotely served calls\n\nRemotely served edits are less likely to be blocked by the read-before-write rule.\n\n**What**\n\nThe rule that a file must be read before it is written or edited now treats calls served remotely as a separate case instead of always consulting the permission mode, so those calls are less likely to be blocked. Write's input validation also drops an async precheck that returned error code 15.\n\n**Details**\n\n- Both `tengu_write_tool_not_read_hypothetical` and `tengu_edit_tool_not_read_hypothetical` gain a `servedCall` field recording whether the call came in remotely.\n- The guard computes that up front and folds it into the decision to skip.\n- Applies unconditionally, with no flag.\n\n**Evidence**\n\n`tengu_write_tool_not_read_hypothetical`, `tengu_edit_tool_not_read_hypothetical`\n\n- Area: File Editing\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}