freeze

To restrict file edits to a specific directory, you can lock an edit boundary using a PreToolUse hook that compares file_path against your configured directory, blocking any Write or Edit operations outside that path.

Yes, you can prevent accidental code changes by applying a session-based edit boundary that blocks Write and Edit operations outside your specified directory, keeping debugging safely scoped to a single module.

You set up a prehook edit boundary by specifying a target directory, which stores a per-session boundary in a state file and uses a PreToolUse hook to intercept and validate file modifications against the allowed path.

The edit freeze boundary is fully reversible; you can remove the restriction using an explicit unfreeze command or simply end your current interactive session to clear the contained edit boundary state.

Yes, you need python3 installed in your environment, as the underlying mechanism relies on it to execute the PreToolUse hook and manage the state file that tracks your active edit boundary.

The best way to lock edits to a folder for testing is to apply a per-session edit boundary that utilizes a PreToolUse hook, preventing any file modifications outside the user-specified directory.