{"version":"2.1.248","anchor":"restricted-confines-file-tools-to-the-working-directory","canonical_anchor":"restricted-confines-file-tools-to-the-working-directory","heading":"--restricted confines file tools to the working directory","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/restricted-confines-file-tools-to-the-working-directory","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### `--restricted` confines file tools to the working directory\n\nRestricted sessions block file paths outside the working directory with no approval offered.\n\n**What**\n\nIn 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.\n\n**Details**\n\n- 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.\n- Same `--restricted` flag as elsewhere; no server-side gate.\n\n**Evidence**\n\n`--restricted confines the file tools to the working directory.`\n\n- Area: Permissions\n- Names: `--restricted`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}