Edits and writes driven from another session are checked before and after path resolution, and can be refused.
What's wrong with this entry?
When 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.
- Only reached when the tool call carries a remote-call context; ordinary local edits are untouched.
- On the remote path the tools skip local-session side effects: dynamic skill directory triggers, the
beforeFileEditedsession hook, and change/save notifications to language servers. Those run only when there is no remote call. - The file-permission dialog treats a remote-driven input as a remote workspace.
- References to the remote-call context across the bundle went from 13 to 38.
Served file call refused at write time
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