freeze

To restrict code edits to a single directory, you can use a session boundary that blocks Edit and Write operations outside an allowed path while still permitting Read access, preventing accidental modifications to other modules.

A PreToolUse hook for scoping file changes is a mechanism that intercepts Edit and Write actions before execution, running a validation script to ensure operations only occur within a specified directory boundary.

You can prevent accidental writes outside a specific folder by setting a per-session edit boundary that actively blocks Write operations beyond the defined path, confining all modifications to the intended module.

Yes, you can still read files outside the allowed path when directory edits are frozen, as the boundary only blocks Edit and Write operations while allowing Read access for reference.

No, freezing a directory boundary does not require external dependencies, as it operates using a state file and a bash hook script to enforce the edit restrictions natively within the session.

The best way to confine modifications to one module is to establish a temporary directory boundary that restricts all Edit and Write actions to that specific scope for the duration of the session.