freeze

To restrict edits outside a specific directory, you can set a freeze boundary that stores the allowed path in a state file and validates Edit/Write operations in real time via a PreToolUse hook, blocking any changes outside that scope.

Yes, you can scope code changes to a single folder by setting a freeze boundary, which enforces a directory boundary for the current session and ensures all edits remain within the approved module or folder during debugging.

A PreToolUse hook enforces directory boundaries by intercepting Edit and Write operations, checking the target path against an allowed directory stored in a state file, and blocking any operation that falls outside the frozen path.

The best way to prevent accidental modifications during code reviews is to set a directory boundary that persists to a state file, blocking any edits outside the frozen path and keeping changes safely contained within the reviewed scope.

Yes, the freeze safeguard works for both Edit and Write operations, evaluating each request in real time through a hook script to ensure the target file resides within the frozen directory before allowing the modification to proceed.

To set up a directory freeze boundary, ask Claude to specify the directory you want to allow edits in, which saves the path to a state file and activates the PreToolUse hook to validate all subsequent file operations against that boundary.