freeze

You can restrict file edits to a specific directory by setting a freeze boundary in a state file, which the system reads to confine changes. This enforces an explicit directory boundary, preventing accidental modifications outside the target module.

Directory freeze enforcement locks edits to a single folder during a session. It works by reading a defined boundary from a state file and applying a PreToolUse hook that actively blocks any edit operations attempted outside that specified directory.

Yes, you can lock code changes to a single module for scope-limited debugging. By defining a directory boundary, the system ensures that all edits remain confined within the intended folder, preventing unintended modifications to other parts of the codebase.

The best way to prevent accidental modifications outside a target folder is to establish a directory freeze. This creates an explicit boundary enforced by a PreToolUse hook, which blocks edits outside the specified path for the duration of your session.

Yes, the directory edit restriction works automatically. Once you specify the directory to freeze, the system reads this boundary from a state file and automatically enforces it via a PreToolUse hook, blocking any subsequent edit attempts outside that folder.

You should not use a directory freeze when your work requires modifying multiple directories or modules simultaneously. It is specifically designed for debugging or scope-limited changes, and will block any edits attempted outside the defined boundary.