freeze

You restrict file edits by setting a directory boundary that blocks any edit operations outside a specified folder. This session-scoped state ensures changes remain confined to that directory, preventing accidental cross-project modifications.

Directory-boundary enforcement is a mechanism that controls edits within a specific folder, blocking operations outside that boundary. It enables safer debugging by preventing accidental changes to files elsewhere in the project during a focused session.

Yes, you can reset the freeze boundary as needed. The session-scoped state persists the allowed directory for the current session, allowing you to reconfigure the restriction so edits can proceed in a different folder.

Yes, the edit restriction uses PreToolUse integration to automatically check target file paths before Edit or Write operations. It loads the freeze directory from a state file and denies any operations attempting to modify files outside that boundary.

Edits are blocked outside the frozen directory because the boundary enforcement compares target file paths against your specified folder and denies operations outside it. This restriction prevents accidental cross-project changes during your session.