freeze

To prevent accidental file modifications outside your target path, you can lock edits to a specific directory for the current session. This implements a PreToolUse hook that intercepts tools and blocks off-boundary edit and write operations.

A PreToolUse hook for blocking file modifications is a mechanism that intercepts tool calls before execution to validate target file paths. It enforces a directory restriction by checking requested paths against a stored boundary and aborting operations that fall outside the approved scope.

To set an editing boundary for debugging, you define a freeze boundary that restricts edits to your chosen directory for the current session. This boundary blocks any write operations outside the target path, ensuring your debugging work does not trigger unintended changes elsewhere.

Yes, you can bind write operations to a single directory for module-focused work by activating a session hook. This hook enforces a strict directory restriction, verifying every target file path against your defined boundary and blocking any edits that fall outside that module path.

Yes, the freeze hook blocks both Edit and Write operations outside the defined boundary. It enforces the directory restriction by validating target file paths during the PreToolUse phase, ensuring no modifications occur beyond the stored boundary during the active session.