{"version":"2.1.246","anchor":"edit-and-write-check-admission-before-writing-on-remote-driv","canonical_anchor":"edit-and-write-check-admission-before-writing-on-remote-driv","heading":"Edit and Write check admission before writing on remote-driven calls","tier":"notice","area":"Remote Execution","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/edit-and-write-check-admission-before-writing-on-remote-driv","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Edit and Write check admission before writing on remote-driven calls\n\nEdits and writes driven from another session are checked before and after path resolution, and can be refused.\n\n**What**\n\nWhen an Edit or Write call arrives from another session rather than from your local one, the tools now run an admission check before writing and re-check it after the file path is resolved. A refusal comes back as an `invalid_request` verdict with the reason `served_floor`, and nothing is written.\n\n**Details**\n\n- Only reached when the tool call carries a remote-call context; ordinary local edits are untouched.\n- On the remote path the tools skip local-session side effects: dynamic skill directory triggers, the `beforeFileEdited` session hook, and change\/save notifications to language servers. Those run only when there is no remote call.\n- The file-permission dialog treats a remote-driven input as a remote workspace.\n- References to the remote-call context across the bundle went from 13 to 38.\n\n**Evidence**\n\n`Served file call refused at write time`\n\n- Area: Remote Execution\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}