freeze

Restricting file edits to a specific directory involves enforcing a boundary on Edit and Write operations that blocks modifications outside the allowed path. This prevents accidental changes during debugging or scoped work by preserving normal Read access.

Yes, you can still read files outside the allowed directory boundary after freezing edits. The restriction blocks Edit and Write operations while preserving normal Read access for files outside the designated folder.

A pretool hook for blocking out-of-bound file modifications is a mechanism that intercepts Edit and Write operations before execution. It checks the target path against a per-session state file and denies attempts on files outside the allowed directory.

You can change or remove the editable folder boundary by updating the per-session state file that persists the restriction. This provides an easy way to modify the allowed directory path or clear the boundary entirely during the current session.

You should use a session boundary to lock edits to a single folder during debugging, module isolation, or scoped work. It ensures all changes stay within a single directory and reduces the risk of accidental modifications to other project files.