freeze

To restrict file edits to a specific directory during a coding session, you set a boundary path that blocks any modifications outside that folder. This prevents accidental changes to other parts of the project while you debug.

Yes, you can lock your editing scope to prevent accidental modifications by defining a restricted directory. The session enforces this boundary, denying any write operations attempted on files outside the specified path.

A PreToolUse hook enforces directory restrictions by intercepting edit and write operations before they execute. It checks the target file path against the boundary stored in the session state and denies access if it falls outside.

Yes, you need Python 3 installed in your environment to run the session-scoped edit boundary tool. The script relies on Python to execute the PreToolUse hook and manage the restriction state.

To change or remove an active directory freeze boundary, you use the /freeze command to set a new path or the /unfreeze command to remove the restriction entirely. This updates the boundary state persisted for the current session.

The best way to maintain module-level integrity when debugging a large project is to constrain your edits to the specific module directory. Locking the session scope prevents unintended write operations from affecting unrelated project files.