Reads from another session go through an admission check and re-verify the path after reading.
What's wrong with this entry?
Reads driven from another session now resolve the file through an admission check that must return "admitted", otherwise the read is refused back to the caller as an invalid request. After the bytes come off disk the path is checked again, and if it no longer points where it did, the cached read state is dropped and the caller is told to read again.
- Remote-driven reads bypass the read-first guard-skip heuristic and the read dedup cache.
- They also skip dynamic skill directory triggers, skip pending handover reads, and never open an IDE diff tab.
- Local reads take none of these branches; the whole path is conditioned on the call carrying a remote-call context, with no flag involved.
Served file call refused at read 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