freeze

You can restrict file edits by applying a directory boundary that uses a PreToolUse hook to check target file paths and block Write or Edit operations outside the allowed folder for the current session.

Session-boundary edit control is a workflow safety mechanism that prevents unintended code changes by locking modifications to a defined folder, ensuring debugging or module isolation does not impact unrelated files elsewhere.

You lock down edits by specifying a target directory to freeze, which applies a state file boundary that denies any Edit or Write operations targeting file paths outside that specific folder.

Yes, edit control blocks Write operations by using a PreToolUse hook to evaluate the target file path against a stored boundary, denying any attempt to modify files outside the defined directory.

Use a directory boundary to isolate module modifications when debugging or scoping changes to a single folder, preventing accidental edits to unrelated code in other parts of the project.

The limitation of freezing edits is that the boundary restricts all Write and Edit operations to a single folder for the entire session, meaning any required modifications outside that path will be denied until the boundary is removed.