freeze

You can restrict file edits to a specific directory by setting a directory boundary that blocks Edit and Write operations outside the allowed path. This persists for the current session via a state file, preventing accidental modifications to unrelated code.

Yes, you can lock down edits to one folder to ensure safe debugging. By enforcing a directory boundary, the tool blocks any file modifications outside the user-defined path, keeping your debugging fixes scoped and isolated.

A PreToolUse hook prevents modifications outside a designated path by intercepting file operations before they execute. It checks the target path against a stored directory boundary state and blocks Edit or Write operations that fall outside the allowed scope.

The best way to scope changes to a single module is to apply a session boundary that locks edits to that specific directory. This restricts all file modifications to the defined path, ensuring the rest of the codebase remains untouched.

Yes, the mechanism relies on a Bash script to store the boundary state. This script works with a PreToolUse hook to persist the directory boundary for the session and actively block Edit and Write operations outside that scope.