freeze

You can restrict file edits to a specific directory boundary by applying a freeze state that blocks all Write and Edit operations outside the target folder path while still allowing read-only access for research and verification.

To prevent accidental modifications to sensitive configuration files, enforce an absolute-path boundary with a trailing slash that blocks out-of-scope writes, keeping the restriction active until you explicitly run an unfreeze command.

Yes, the directory boundary works effectively for a repository subset by confining edits to a single folder tree, preventing accidental changes to production-related files outside the target scope while allowing search operations.

To deactivate the session-persistent edit restriction, you must explicitly run the /unfreeze command, which releases the active freeze state and restores standard file system permissions for Edit and Write operations.

The freeze state mandates the target directory exist before writing to enforce safety guardrails, preventing overly broad boundaries like the root or home ancestors of the configuration folder from accidentally exposing sensitive files.

Yes, you can perform read-only access on files outside the frozen directory scope, as the restriction specifically targets file Edit and Write operations, allowing you to read and search the broader file system for verification.