You'll notice
Useful3 Signal2
Restricted sessions now deny out-of-directory reads and writes outright, with no prompt.
What's wrong with this entry?
Anonymous. No account, no email.
--restricted
What
In a --restricted session, a read or write aimed at a path outside the working directory is now denied explicitly instead of falling through to a permission prompt. The denial text is new in this build.
Details
- One helper produces the denial and is wired into both the read decision and the write decision; the write path calls the read decision with the restricted flag forced on.
- The denial reason is mapped to the restricted-mode circuit breaker so repeated attempts are handled as a group.
- Session-level only: it depends on how the session was launched, not on any server-side flag.
Evidence
is outside ${u}; --restricted confines the file tools to the working directory.
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.