Restricted sessions block file paths outside the working directory with no approval offered.
What's wrong with this entry?
In a restricted session, file tools now refuse paths outside the working directory with a dedicated message, and an unsafe path is marked as not approvable rather than offering the usual classifier-based approval prompt. Restricted sessions also lose the leniency that remote mode previously granted to the path safety check.
- The safety check is now asked whether the session is remote and not restricted, rather than just remote; the artifact database read path picks this up when saving fetched documents into an output directory.
- Same
--restrictedflag as elsewhere; no server-side gate.
--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.