freeze

You can restrict file edits to a specific directory by setting a freeze boundary that blocks any modifications outside the designated path. This enforces scope control and prevents accidental drift during focused work.

To prevent accidental edits outside a folder, a PreToolUse hook checks file operations and denies modifications beyond the boundary. This ensures debugging changes remain scoped to the target module.

A PreToolUse hook for blocking file modifications intercepts edit and write operations before execution, checking them against a persistent state file to deny any changes outside a set directory boundary.

Yes, you can lock edits to a single module and persist that boundary across a session. A state file maintains the restriction until explicitly reset, keeping the scope active throughout your workflow.

Yes, the freeze boundary works without additional dependencies. It relies solely on a persistent state file and a PreToolUse hook to enforce directory restrictions, requiring no external components.

You should not use a directory freeze boundary when your task requires editing multiple modules or making cross-directory references. It is designed for isolated debugging and restricts all edits outside the specified path.